{chain} path param is a friendly slug. Map of slug → CAIP-2
chain ID + Aegis coverage below.
{chain} | CAIP-2 | Aegis |
|---|---|---|
eth | eip155:1 | ✅ |
bsc | eip155:56 | ✅ |
tron | (TRX native) | ✅ |
polygon | eip155:137 | — |
base | eip155:8453 | — |
arbitrum | eip155:42161 | — |
optimism | eip155:10 | — |
avalanche | eip155:43114 | — |
fantom | eip155:250 | — |
btc | (BTC native) | — |
sol | (SOL native) | — |
ltc | (LTC native) | — |
400 unsupported_network.
Aegis is the single verdict surface. Where the on-chain graph is
sparse, additional commercial scoring runs under the hood (opt-in) and
is folded into the same Aegis verdict — there is no separate
multi-provider tier to select.
Address format
| Chain family | Format | Case-handling |
|---|---|---|
| EVM (eth, bsc, polygon, base, arbitrum, optimism, avalanche, fantom) | 0x + 40 hex | Lowercased server-side |
| TRON | base58 (T…34 chars) | Case-sensitive — sent as-is |
| BTC | base58 / bech32 | Case-sensitive |
| SOL | base58 (32 chars) | Case-sensitive |
| LTC | base58 / bech32 | Case-sensitive |
0x6b17…
EVM address can be sent in any case and we’ll normalise.
Settlement chain
Independent of{chain}. Today the x402 quote always settles on
Base mainnet (or Base Sepolia for testnet calls), regardless of
which chain you’re querying. Multi-chain settlement is on the
roadmap.