# Cross-Chain Bridge Route Lookup

> Cross-Chain Bridge Route Lookup is a paid API for AI agents from x402helper.xyz, paid per call via x402, $0.065/call, status unknown (last checked 2026-10-31).

Returns bridging route information for moving crypto assets between blockchain networks (e.g. Ethereum to Base, Polygon to Arbitrum).

## Facts

- Endpoint: GET https://x402helper.xyz/89e509/bridge/route?utm_source=zero.xyz
- Price: $0.065/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cross-chain-bridge-route-lookup-bccbd35e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vSz_lyABpjOlP95OForCP

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability cross-chain-bridge-route-lookup-bccbd35e
```

Example prompt: What's the bridge route for moving 500 USDC from Ethereum to Base?

## When to prefer this

Use this endpoint when an AI agent needs to programmatically discover cross-chain bridge routes between supported chains (Ethereum, Arbitrum, Base, Optimism, Polygon, BSC, Solana) and is willing to pay a small per-call USDC micropayment via the x402 protocol. Prefer this for automated DeFi workflows where routing logic must be resolved on demand.

## Known failure modes

- Unsupported source or destination chain returns empty or failed route
- Invalid or unrecognized asset ticker may return no result
- Missing required src or dst query parameters causes request failure
- Payment of 0.065 USDC via x402 protocol required; missing payment returns 402 error
- Network timeout or upstream routing service unavailable

## How this service works

X402 micropayments server — AI agents pay USDC for OFAC screening, rates, and billing verification.

## Output

Returns a JSON object with a 'result' field containing bridge route details and a 'success' boolean indicating whether a route was found for the given source chain, destination chain, asset, and amount.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "src",
      "dst"
     ],
     "properties": {
      "dst": {
       "type": "string",
       "default": null,
       "description": "Destination chain (e.g. arbitrum, optimism, base, solana)."
      },
      "src": {
       "type": "string",
       "default": null,
       "description": "Source chain (e.g. ethereum, arbitrum, base, polygon, bsc)."
      },
      "asset": {
       "type": "string",
       "default": null,
       "description": "Asset ticker to move (e.g. USDC, ETH, WBTC). Optional; echoed."
      },
      "amount": {
       "type": "number",
       "default": null,
       "description": "Amount to move, for context. Optional; echoed."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {},
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cross-chain-bridge-route-lookup-bccbd35e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402helper.xyz](https://www.zero.xyz/host/x402helper.xyz/llms.txt)