List bridgeable tokens for a given chain via x402-paid DeFi Intelligence API.
What it does
The `/defi/bridge/tokens` endpoint is part of the DeFi Intelligence API hosted at defi.hugen.tokyo. It returns the list of tokens available for cross-chain bridging on a specified chain. You provide a chain key (e.g., 'eth', 'pol', 'bsc') as a query parameter, and the endpoint returns the bridgeable tokens for that chain. Payment is handled via the x402 protocol at $0.01 per call, settled in USDC or USDT on Base.
This endpoint belongs to a broader suite of 26 DeFi security and data endpoints covering token audits, rugpull detection, phishing checks, bridge routing (quotes, routes, status, chains, tokens, tools), gas prices, protocol analytics (TVL, fees, info), token prices, stablecoin data, DEX volume, NFT security, address security, dApp audits, approval security, malicious address checks, and EVM transaction simulation. All endpoints follow the same x402 pay-per-call model with no API keys or rate limits required. Alternative access methods include a broker API (with a free API key providing $0.05 credit), an MCP server at mcp.hugen.tokyo, and a Python SDK (`x402-pay`).
The endpoint accepts GET requests with a required `chain` query parameter (a chain key string). Response schemas are not explicitly documented beyond the OpenAPI stub, but the endpoint is confirmed live via a 402 challenge. The API is versioned at 0.1.0, suggesting early-stage development.
Capabilities
Use cases
- —Querying which tokens can be bridged from a specific blockchain before initiating a cross-chain transfer
- —Building a bridge UI that dynamically populates token selectors based on the selected source chain
- —Automated agents checking token bridge availability across chains as part of a DeFi workflow
- —Portfolio tools verifying whether a user's tokens are bridgeable to a target chain
Fit
Best for
- —Agents or apps that need programmatic access to bridgeable token lists per chain
- —Developers building cross-chain bridge interfaces without managing upstream API keys
- —Pay-per-call usage where no subscription or rate-limit management is desired
Not for
- —High-frequency polling where per-call costs would accumulate quickly
- —Use cases requiring detailed bridge routing or quotes (use /defi/bridge/quote or /defi/bridge/routes instead)
- —Users who need free or open-source token list data without payment
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/tokens?chain=eth')
print(response.json())Example
Request
{
"url": "https://defi.hugen.tokyo/defi/bridge/tokens?chain=eth",
"method": "GET"
}Endpoint
Quality
The endpoint is confirmed live via a 402 x402 challenge, and a full OpenAPI 3.1 spec is available with parameter definitions. However, response schemas are empty stubs (no documented response shape), no example responses are provided, and the API is at version 0.1.0. Pricing is clear ($0.01/call in USDC on Base).
Warnings
- —Response schema is not documented — the OpenAPI spec uses an empty schema object for the 200 response.
- —API version 0.1.0 indicates early-stage; breaking changes may occur.
- —No example response data is available from the probe or crawl material.
- —The root URL (defi.hugen.tokyo/) returns 404; only the /docs and specific endpoints are functional.
Citations
- —The endpoint requires a 'chain' query parameter described as a chain key (e.g., 'eth', 'pol').https://defi.hugen.tokyo/docs
- —The API comprises 26 DeFi security and data endpoints with x402 pay-per-call pricing.https://defi.hugen.tokyo/docs
- —Payment is $0.01 USDC on Base per call, with USDC (6 decimals) and USDT (6 decimals) accepted.https://defi.hugen.tokyo/defi/bridge/tokens
- —Alternative access via broker API, MCP server, and x402-pay Python SDK is available.https://defi.hugen.tokyo/defi/bridge/tokens
- —API version is 0.1.0.https://defi.hugen.tokyo/docs