Skip to main content
POST
/
check-address
Aegis full 4-tier verdict (SDN + consensus + 1-hop + BFS)
curl --request POST \
  --url https://api.aegis-kyt.com/v2/check-address \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "address": "<string>",
  "network": "<string>"
}
'
{
  "schema_version": 1,
  "address": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t",
  "network": "TRON",
  "provider": "Aegis",
  "decision": "reject",
  "verdict": {
    "ok": true,
    "risk_level": "sanctioned",
    "risk_score": 100,
    "risk_categories": [
      "sanctioned"
    ],
    "sdn_match": {
      "entity_name": "EXAMPLE DESIGNATED ENTITY",
      "programs": [
        "SDN"
      ],
      "listing_date": "2025-11-14"
    },
    "consensus_found": true,
    "source_count": 3,
    "confidence": 0.92,
    "tier3_applied": true,
    "tier4_applied": true,
    "sanctions_exposure_share": null,
    "vasp_attribution": null,
    "fallback_used": []
  },
  "billing": {
    "model": "ledger",
    "charged_usd": "1.000000",
    "balance_usd": "42.500000",
    "monthly_spent_usd": "12.300000",
    "monthly_cap_usd": "500.000000"
  },
  "elapsed_ms": 1840
}
Auth: Required · Billing: per your plan (commercial agreement)
Run the full Aegis 4-tier verdict on a single address. Aegis-only — third-party providers run under the hood when the on-chain graph is sparse (opt-in), not as a selectable option.

Request

curl -X POST https://api.aegis-kyt.com/v2/check-address \
  -H "Authorization: Bearer aeg_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "address": "TScSLnUodZVsgoGchZspDoimDjDB9bwqVv",
    "network": "TRON"
  }'
FieldTypeNotes
addressstringEVM hex (auto-lowercased) or base58 (TRON/BTC/SOL — case preserved)
networkstringCase-insensitive. Must be one of .
Optional headers:
HeaderPurpose
Idempotency-Key: <≤64 chars>Replay-safe within 24h. Same key + same body → cached response, no charge. Different body → HTTP 409.

Response 200

Full Aegis 4-tier verdict (Tier 0 SDN + Tier 1+2 consensus + Tier 3 1-hop + Tier 4 BFS). Network must be one of for full verdict — others reject with HTTP 400.
{
  "schema_version": 1,
  "address": "TScSLnUodZVsgoGchZspDoimDjDB9bwqVv",
  "network": "TRON",
  "provider": "Aegis",
  "decision": "review",
  "verdict": {
    "ok": true,
    "risk_level": "medium",
    "risk_score": 50,
    "risk_categories": ["mixer-adjacent"],
    "consensus_found": true,
    "source_count": 3,
    "confidence": 0.78,
    "primary_source_slug": "graphsense-tag-pack",
    "label": "TornadoCash 1-hop",
    "sdn_match": null,
    "tier3_applied": true,
    "tier4_applied": false
  },
  "billing": {
    "quota_cost": 1,
    "remaining": 14,
    "monthly_quota": 15,
    "period_start": "2026-05-01"
  },
  "elapsed_ms": 320
}
decision (top-level) is the merchant traffic-light — one of accept · review · reject · unable. Build your accept/block flow on this field. It is the same vocabulary as final.verdict on POST /v2/inspect-address, so both address surfaces speak one decision word:
decisionMeaning
acceptno risk signals found
reviewelevated / borderline — your operator decides
rejecthigh risk (sanctions / criminal exposure)
unableno data to assess — do not treat as clean
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

HTTPcodeWhy
400unsupported_networknetwork not in /v2/networks
401missing_or_invalid_keyBearer header missing or wrong
402quota_exceededmonthly_quota burned; refund cycle on 1st
409idempotency_conflictsame key + different body within 24h
502backend_unavailableAegis engine temporarily unreachable. Charge refunded.

See also

Authorizations

Authorization
string
header
required

Your aeg_… API key from the dashboard (Account → API tab).

Headers

Idempotency-Key
string | null

Body

application/json
address
string
required

On-chain wallet. EVM is lowercased internally; TRON/BTC/SOL preserved.

Required string length: 1 - 120
Examples:

"TScSLnUodZVsgoGchZspDoimDjDB9bwqVv"

"0x21a31ee1afc51d94c2efccaa2092ad1028285549"

network
string
required

Chain identifier. See /v2/networks for allowed values.

Required string length: 1 - 20
Examples:

"TRON"

"ETH"

Response

Successful Response

The response is of type Response Check Address Check Address Post · object.