List supported blockchain chains from a 26-endpoint DeFi security and data API, paid per call via x402.
What it does
The `/defi/chains` endpoint is part of the DeFi Intelligence API hosted at defi.hugen.tokyo. It returns the list of blockchain chains supported by the API's security and data services. The broader API exposes 26 endpoints covering token security audits, address and NFT security checks, rugpull detection, phishing URL checks, transaction simulation, approval security, dApp audits, cross-chain bridge quoting/routing/status, gas prices, protocol analytics (TVL, fees, info), token prices, stablecoin data, and DEX volume. All endpoints are paid per call using the x402 protocol.
The `/defi/chains` endpoint is a simple GET with no required parameters. It costs $0.01 USDC on Base per call according to the x402 challenge. The API supports at least 25 chains, with chain IDs 1 (Ethereum), 56 (BSC), 137 (Polygon), 42161 (Arbitrum), 8453 (Base), and 10 (Optimism) explicitly listed in the probe. No API keys or rate limits are required; payment is handled inline via x402. Alternative access methods include a broker API key, an MCP server at mcp.hugen.tokyo, and a Python SDK (`x402-pay`).
The endpoint is live, returning a 402 payment challenge as expected for x402. The OpenAPI spec (v3.1) is available at `/openapi.json` and a Swagger UI at `/docs`. Response schemas for most endpoints (including this one) are not fully specified in the OpenAPI document — they use empty schema objects — so the exact response shape must be inferred from usage.
Capabilities
Use cases
- —Querying which blockchain networks are supported before making token or address security checks
- —Building a multi-chain DeFi dashboard that dynamically adapts to available chains
- —Agent workflows that need to validate chain support before routing bridge or gas queries
- —Pre-flight checks in automated trading bots to confirm chain coverage
Fit
Best for
- —AI agents needing programmatic DeFi security data across multiple chains
- —Developers building multi-chain DeFi tools without managing multiple upstream API keys
- —Quick chain-support lookups before calling other endpoints in the same API
Not for
- —Direct on-chain transaction execution or signing
- —Historical blockchain data archival or full-node queries
- —Free or high-volume bulk data extraction (each call costs $0.01)
Quick start
# Using the x402-pay Python SDK
pip install x402-pay
import x402_pay
response = x402_pay.get('https://defi.hugen.tokyo/defi/chains')
print(response.json())Endpoint
Quality
The endpoint is live with a valid x402 402 challenge, and a full OpenAPI 3.1 spec is available covering all 26 endpoints. However, response schemas are empty (no defined shape), no example responses are provided, and dedicated documentation pages (pricing, README) return 404. The exact response format for /defi/chains must be inferred.
Warnings
- —Response schemas in the OpenAPI spec are empty objects — actual response shape is undocumented.
- —No dedicated pricing page; price ($0.01 USDC on Base) is only visible in the x402 challenge.
- —Root URL and /pricing, /README, /api all return 404 — documentation is limited to /docs Swagger UI.
Citations
- —The API describes itself as '26 DeFi security and data endpoints — token audits, bridge routing, protocol analytics' with 'one x402 payment per call'.https://defi.hugen.tokyo/docs
- —The /defi/chains endpoint costs $0.01 USDC on Base per call.https://defi.hugen.tokyo/defi/chains
- —The API supports at least 25 chains including chain IDs 1, 56, 137, 42161, 8453, and 10.https://defi.hugen.tokyo/defi/chains
- —Alternative access via broker, MCP, and x402-pay SDK is documented in the x402 challenge.https://defi.hugen.tokyo/defi/chains
- —OpenAPI 3.1 spec is available at /openapi.json.https://defi.hugen.tokyo/docs