Integration guides for AI-agent builders
draconic21 sells SEC EDGAR filings/XBRL, OFAC sanctions screening, US Treasury fiscal data, and a daily agent-economy signal, pay-per-call in USDC on Base via x402. No account, no API key, no subscription — your agent's own wallet pays per call. Every snippet below is real, tested code that runs against the live API.
No Base USDC wallet, or building for a human developer instead of an agent? The sanctions/EDGAR/Treasury endpoints are also published on the RapidAPI Hub — standard API-key auth, card billing (BASIC free · PRO $9.99/mo · ULTRA $29.99/mo), no crypto wallet required.
Pick your stack
Prerequisites
- A wallet on the Base network (chain id 8453) funded with a little USDC — a few dollars covers hundreds of calls at these prices.
- An x402 v2 client library (installed per snippet below) that can sign the "exact" EVM payment scheme (EIP-3009, gasless — no ETH for gas needed on your side).
- Your wallet's private key available to your own process/agent — never share it, never commit it, never paste it into a chat with an AI you don't fully trust with funds.
Which x402 client version works
The x402 ecosystem has two live wire protocols. This API's payment pipeline runs the current x402 v2 SDK (the scoped @x402/* npm packages). Many deployed agents still run the older x402 v1 stack instead — the unscoped x402 / x402-fetch / x402-axios / x402-mcp npm packages (what Vercel's x402-ai-starter pins) or the x402 PyPI package's v1 mode.
| Client stack | Reads the 402 challenge | Can complete a paid call? |
|---|---|---|
x402 v2 — @x402/fetch, @x402/core, official Python x402 v2 client | Yes — PAYMENT-REQUIRED response header | Yes — this is the supported path |
x402 v1 — x402-fetch, x402-axios, unscoped x402 npm/PyPI package, x402-ai-starter | Yes — every paid route's 402 JSON body is genuinely v1-shaped (x402Version:1, accepts[].maxAmountRequired, short chain names like "base") | Not yet — see below |
We verified this directly: a fresh v1 client (x402-fetch@1.2.0, zero-balance throwaway key, no signature ever produced) failed to even parse our old v2-shaped 402 body. That's fixed — every paid route's JSON body is now a real v1 challenge, so a v1 client can discover price/network/recipient. What's still unresolved is paying: a v1 client signs and sends its payment under the legacy X-PAYMENT header, and the installed v2 SDK's server-side payment extraction doesn't read that header for a true v1 payload — a known SDK-level gap, not a Draconic21 design choice. A v1 client hitting a paid route today will keep getting a (correctly-shaped) 402 rather than completing the purchase.
If you're building new: use an x402 v2 client (every snippet in the guides below already does). If you're stuck on v1: your client can now at least discover pricing/terms from the JSON body; full v1 payment support is tracked as an open item.
Routes you can call this way
Every example below targets one specific route to keep the snippet runnable, but the same client works against any draconic21 x402 route. Full list and schemas: /openapi.json.
| Route | Price | What it does |
|---|---|---|
POST /v1/sanctions_screen | $0.006 | OFAC SDN name/wallet screening |
POST /v1/sanctions_delta | $0.008 | OFAC SDN list changes since a date |
POST /v1/edgar_filings | $0.02 | Recent SEC filings by ticker/CIK |
POST /v1/edgar_company_facts | $0.02 | Key XBRL facts by ticker/CIK |
POST /v1/edgar_fulltext_search | $0.02 | Full-text search of SEC filings since 2001 |
POST /v1/signal_latest | $0.03 | Daily agent-economy signal brief |
POST /v1/signal_delta | $0.05 | What changed in Signal since a date |
Runnable source
Each guide above includes its full copy-paste example on this public site. The examples are tested against the live server with payment disabled; they stop at the HTTP 402 challenge until you configure your own wallet. See the public API specification for request and response schemas.