Aegis full 4-tier verdict (SDN + consensus + 1-hop + BFS) — submit
V2 Public API
POST /v2/check-address
Single-provider AML check on one address.
POST
Aegis full 4-tier verdict (SDN + consensus + 1-hop + BFS) — submit
Auth: Required · Billing: per your plan (commercial agreement)
Request
Optional headers:
Response 202 — accepted
result_url every few seconds. Typical completion is 5-90 s; a cold BFS
can take longer. Network must be one of — anything else is
rejected with HTTP 400 before a job is created.
The verdict
Delivered byGET /v2/check-address/{check_id}/result,
which is where the response body and its fields are documented.
decision (top-level) is the merchant traffic-light — one of
accept · review · reject · unable. Build your accept/block flow on
this field:
decision is a probabilistic risk signal, not a command to accept/reject and
not legal advice — the final decision and risk are yours.
verdict.risk_level / verdict.risk_score give the detail behind the
decision; verdict.tier3_applied / tier4_applied show which depth tiers
ran (tier4_applied: false may mean too few transactions for BFS — Tier
0+1+2 still executed).
Errors
Failures of the check itself surface on the poll, not here — this endpoint
only accepts the job.
See also
- V2 introduction
- POST /v2/check-transfer — Transaction Check (KYT)
- GET /v2/check-address//result — the verdict
- GET /v2/balance — what is left to spend
- GET /v2/me/usage — billing snapshot + call history
Authorizations
Your aeg_… API key from the dashboard (Account → API tab).
Headers
Body
application/json
On-chain wallet. EVM is lowercased internally; TRON/BTC/SOL preserved.
Required string length:
1 - 120Examples:
"TScSLnUodZVsgoGchZspDoimDjDB9bwqVv"
"0x21a31ee1afc51d94c2efccaa2092ad1028285549"
Chain identifier. See /v2/networks for allowed values.
Required string length:
1 - 20Examples:
"TRON"
"ETH"
Response
Successful Response
The response is of type Response Check Address Check Address Post · object.

