sseMITupdated 1mo ago
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.
What can you do with Cross Chain Bridge Route API?
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
Install
Add Cross Chain Bridge Route API to your client. Pick the one you use.
claude mcp add --transport sse cross-chain-bridge-route-api https://bridge-routes.api.klymax402.com/mcpcodex mcp add cross-chain-bridge-route-api --url https://bridge-routes.api.klymax402.com/mcp{
"mcpServers": {
"cross-chain-bridge-route-api": {
"url": "https://bridge-routes.api.klymax402.com/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"cross-chain-bridge-route-api": {
"type": "sse",
"url": "https://bridge-routes.api.klymax402.com/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"cross-chain-bridge-route-api": {
"url": "https://bridge-routes.api.klymax402.com/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"cross-chain-bridge-route-api": {
"serverUrl": "https://bridge-routes.api.klymax402.com/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
1 tool
Cross Chain Bridge Route API exposes one tool to a connected agent.
- bridge_find_best_route
- POST
Score
70 / 100
Good
- Documentation25/25
- Maintenance16/25
- Trust13/20
- Capability4/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 44 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 1 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.1.0Latest | May 16, 2026 |
| 1.0.0 | Apr 12, 2026 |