Synchronizing
Architectural Primitives

Glossary and quick reference

Every term used across this documentation, followed by the facts you are most likely to need while integrating.

Glossary

TermMeaning
TenantA client organisation using Aegis.
Application / caseOne counterparty’s onboarding record.
PairA form plus a risk engine, bound and validated together.
Intake labelThe pointer that makes a pair live and selectable.
Related partyA person or entity screened for an application: a UBO, director, or the company itself.
Analyst sign-offThe mandatory analyst confirmation of criteria the form cannot answer.
Maker-checkerTwo-person approval: one proposes, a different admin approves.
Completeness gateThe conditions that must all pass before an approval is allowed.
Screening exceptionAn attributed MLRO sign-off allowing a case to proceed despite a blocking screening result.
EscalationA rule forcing the risk class to High regardless of the score.
Information requestA structured ask your team sends after submission: questions, corrections to specific answers, or documents, answered in the applicant portal over one or more rounds.

Quick reference

ItemValue
Compliance dashboardhttps://aegis-outpost.theauroraedge.com
Applicant portalhttps://aegis-gateway.theauroraedge.com
Onboarding APIhttps://aegis-api.theauroraedge.com
API authenticationAuthorization: Bearer aegis_<key-id>_<secret>
Provision and get a linkPOST /v1/login-sessions
Provision onlyPOST /v1/applications
Sign-in link lifetime3 days, single use (read expiresAt)
Rate limits60 per minute per key, 240 per minute per IP
Application readsGET /v1/applications/{clientId}
Outcome reportingWebhooks trigger reconciliation; application reads provide current status
Webhook notificationsSigned HTTP POST events; see Webhooks and callbacks

Endpoint contracts are in API reference, and event delivery is in Webhooks and callbacks, and the surfaces are introduced on the documentation overview.