bridge-routes-x402
Finds best cross-chain bridge routes across 60+ chains and 18+ bridges, comparing fees and time, with pay-per-call via x402 USDC micropayments.
README
Cross-Chain Bridge Route API
Best cross-chain bridge routes via LI.FI -- 60+ chains, 18+ bridges, fees and time compared. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"bridge-routes": {
"url": "https://bridge-routes.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
curl "https://bridge-routes.api.klymax402.com/api/route?fromChain=...&toChain=...&token=...&amount=..."
# -> 402 Payment Required, with an x402 payment challenge in the response body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
bridge_find_best_route |
GET | /api/route |
$0.008 | Find the best cross-chain bridge route |
bridge_find_best_route |
POST | /api/route |
$0.008 | Find the best cross-chain bridge route (POST variant) |
bridge_find_best_route
Use this when you need to bridge tokens between different blockchains. Returns ranked bridge routes with fees and timing in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
fromChain |
string | yes | Source chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche) |
toChain |
string | yes | Destination chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche) |
token |
string | yes | Token symbol to bridge (e.g. USDC, USDT, ETH, WETH) |
amount |
string | yes | Amount in smallest unit (e.g. 1000000 for 1 USDC with 6 decimals, 1000000000000000000 for 1 ETH) |
toToken |
string | no | Destination token symbol if different from source (optional, defaults to same as token) |
Returns
routes-- array of bridge options ranked by best valuebridgeProvider-- which bridge protocol (Stargate, Across, Hop, Connext, etc.)estimatedTime-- expected bridge completion time in secondsfee-- total bridging fee in USDamountReceived-- expected output amount on destination chainsteps-- detailed step-by-step route (approve, bridge, swap if needed)
Example response:
{"routes":[{"bridgeProvider":"Stargate","estimatedTime":60,"fee":0.85,"amountReceived":"999.15","steps":["approve USDC","bridge via Stargate"]}],"fromChain":"Ethereum","toChain":"Base","token":"USDC"}
When to use: moving assets cross-chain to find the cheapest and fastest bridge. Essential for multi-chain portfolio management.
Not for: gas prices (use gas_get_current_price).
bridge_find_best_route
Use this when you need to bridge tokens between different blockchains. Returns ranked bridge routes with fees and timing in JSON. POST variant of bridge_find_best_route -- same params passed as JSON body instead of query string.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
fromChain |
string | yes | Source chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche) |
toChain |
string | yes | Destination chain ID (1=Ethereum, 8453=Base, 42161=Arbitrum, 10=Optimism, 137=Polygon, 56=BSC, 43114=Avalanche) |
token |
string | yes | Token symbol to bridge (e.g. USDC, USDT, ETH, WETH) |
amount |
string | yes | Amount in smallest unit (e.g. 1000000 for 1 USDC with 6 decimals, 1000000000000000000 for 1 ETH) |
toToken |
string | no | Destination token symbol if different from source (optional, defaults to same as token) |
Returns
routes-- array of bridge options ranked by best valuebridgeProvider-- which bridge protocol (Stargate, Across, Hop, Connext, etc.)estimatedTime-- expected bridge completion time in secondsfee-- total bridging fee in USDamountReceived-- expected output amount on destination chainsteps-- detailed step-by-step route (approve, bridge, swap if needed)
Example response:
{"routes":[{"bridgeProvider":"Stargate","estimatedTime":60,"fee":0.85,"amountReceived":"999.15","steps":["approve USDC","bridge via Stargate"]}],"fromChain":"Ethereum","toChain":"Base","token":"USDC"}
When to use: moving assets cross-chain to find the cheapest and fastest bridge. Essential for multi-chain portfolio management.
Not for: gas prices (use gas_get_current_price).
Example agent prompts
- "Bridge tokens between different blockchains"
- "Bridge tokens between different blockchains"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (
eip155:8453) - Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。