Why x402
Most data APIs gate access behind subscriptions, key issuance, and per-route rate limits — friction that AI agents can’t navigate autonomously. x402 turns the HTTP 402 status code into a stateless protocol:- Agent requests the resource.
- Server replies
402with a stablecoin quote (asset, amount, recipient, expiry). - Agent signs an EIP-3009 transferAuthorization for the quoted USDC.
- Agent retries with
X-PAYMENT: <base64 proof>; server verifies, settles, and serves the resource.
What we sell
Three paid tiers (all settled in USDC on Base):| Tier | Price | Returns |
|---|---|---|
| Screen | $0.10 | All per-source labels we have for the address plus the Aegis consensus risk score + categories — one tier, one settlement |
| Check Address | $1.00 | Aegis full 4-tier verdict — SDN + multi-source consensus + 1-hop inheritance + BFS exposure |
| Check Transfer | $0.50 | Transaction Check (KYT) — decode a tx, run Tier 4 BFS per sender, apply the Aegis Standard policy, return PolicyAlerts |
- GET /.well-known/x402.json — service discovery (price LUT)
- GET /health — plain-text
ok
Powered by
- 44 ingest sources continuously refreshed: OFAC SDN, Tether blacklist, GraphSense tagpacks, DefiLlama protocol catalog, Arkham deanon, hack-attribution databases, exchange Proof-of-Reserves, and more.
- ~795,000 label claims across 11 EVM + non-EVM chains.
- Aegis 4-tier consensus: SDN exact match → 17-source consensus → 1-hop inheritance from neighbours → BFS multi-hop exposure with per-category aggregation.
Get started
Quickstart
Five minutes from
curl to your first paid call.Authentication
How x402 actually works on the wire.
Endpoints
Per-tier reference with request/response schemas.
Networks & categories
Supported chains, risk taxonomy, error codes.

