List all chains supported by the DeFi Intelligence bridge routing API, paid per call via x402.
What it does
The `/defi/bridge/chains` endpoint is part of the DeFi Intelligence API hosted at defi.hugen.tokyo. It returns the set of blockchain networks supported by the bridge routing subsystem. This is a simple GET request with no required parameters — it enumerates available chains so callers can discover valid source and destination networks before requesting bridge quotes or routes.
The DeFi Intelligence API exposes 26 endpoints covering token security audits, rugpull detection, phishing checks, NFT security, address screening, bridge routing (quotes, routes, status, chains, tokens, tools), gas prices, protocol analytics (TVL, fees, info), token prices, stablecoin data, DEX volume, dApp security, and EVM transaction simulation. All endpoints are gated by x402 micropayments — $0.01 USDC on Base per call — with no API keys or rate limits required. Alternative access methods include a broker API (with a free key providing $0.05 credit), an MCP server at mcp.hugen.tokyo, and a Python SDK (`x402-pay`).
The endpoint returned a valid 402 challenge during probing, confirming it is live. The challenge lists 30 supported chains (with Ethereum and Polygon shown as examples). Response schemas for this endpoint are not detailed in the OpenAPI spec beyond a generic 200 JSON response, so the exact shape of the returned chain list is not documented.
Capabilities
Use cases
- —Discover which blockchains are available for cross-chain bridge operations before requesting a quote
- —Build a chain-selector UI for a bridge aggregator frontend
- —Validate user-supplied chain IDs against the set of supported networks
- —Feed chain availability data into an automated DeFi agent workflow
Fit
Best for
- —Agents or apps that need to enumerate bridge-supported chains before routing
- —Developers building cross-chain bridge UIs or bots
- —Quick lookups of supported networks without managing API keys
Not for
- —Executing actual bridge transactions (this only lists chains, not routes or execution)
- —Free or high-volume bulk chain data needs (each call costs $0.01)
- —Non-crypto use cases
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
response = x402_pay.get('https://defi.hugen.tokyo/defi/bridge/chains')
print(response.json())Example
Response
{
"chains": [
{
"id": 1,
"key": "eth",
"name": "Ethereum"
},
{
"id": 137,
"key": "pol",
"name": "Polygon"
},
{
"id": 8453,
"key": "bas",
"name": "Base"
}
]
}Endpoint
Quality
The endpoint is confirmed live via a 402 challenge, and a full OpenAPI spec is available. However, the response schema for this specific endpoint is empty (no documented fields), no example responses are provided in the docs, and the crawled pages beyond /docs returned 404. The example response above is inferred from the challenge payload and is not authoritative.
Warnings
- —Response schema for /defi/bridge/chains is not defined in the OpenAPI spec — the 200 response schema is empty.
- —Example response JSON is inferred from the x402 challenge snippet, not from actual endpoint documentation.
- —No dedicated pricing page found; $0.01 per call is stated only in the x402 challenge notice.
Citations
- —The DeFi Intelligence API has 26 endpoints covering token audits, bridge routing, and protocol analytics with x402 payment per call.https://defi.hugen.tokyo/docs
- —Payment is $0.01 USDC on Base per call.https://defi.hugen.tokyo/defi/bridge/chains
- —The x402 challenge lists 30 supported chains.https://defi.hugen.tokyo/defi/bridge/chains
- —Alternative access via broker API, MCP server, and x402-pay Python SDK is available.https://defi.hugen.tokyo/defi/bridge/chains
- —The /defi/bridge/chains endpoint is a GET with no required parameters.https://defi.hugen.tokyo/docs