x402basequality 0.62

Cross-chain bridge route discovery via x402 — find optimal bridging paths across EVM chains.

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://defi.hugen.tokyo/defi/bridge/routes

What it does

The `/defi/bridge/routes` endpoint is part of the DeFi Intelligence API hosted at defi.hugen.tokyo. It accepts a POST request with JSON body containing route parameters and returns advanced bridge routing options across supported chains. The endpoint is one of 26 DeFi-focused x402-payable endpoints offered by this service, which aggregates data from 3+ upstream providers behind a single pay-per-call interface.

This specific endpoint focuses on cross-chain bridge route discovery — given source/destination chains, tokens, and amounts, it returns available bridging paths with estimated gas costs. A companion `/defi/bridge/quote` endpoint provides simpler quote lookups, while `/defi/bridge/status`, `/defi/bridge/chains`, `/defi/bridge/tokens`, and `/defi/bridge/tools` round out the bridge-related tooling. The broader API also covers token security audits, rugpull detection, phishing checks, NFT security, protocol analytics (TVL, fees), gas prices, token prices, and more.

Payment is $0.02 USDC on Base per call via the x402 protocol. No API keys or rate limits are required for direct x402 usage. Alternative access methods include a broker API (with free API key and $0.05 credit), an MCP server at mcp.hugen.tokyo, and a Python SDK (`pip install x402-pay`). The endpoint returned a valid 402 challenge on probe, confirming it is live.

Capabilities

cross-chain-bridge-routingbridge-route-discoverymulti-chain-bridgingdefi-datax402-paymentpay-per-callno-api-key

Use cases

  • —Finding optimal cross-chain bridge routes for token transfers between EVM chains
  • —Building automated bridging workflows in trading bots or portfolio rebalancers
  • —Comparing bridge options (gas cost, speed) before executing a cross-chain transfer
  • —Integrating bridge route discovery into wallet or DeFi dashboard UIs
  • —Agent-driven cross-chain asset movement with pay-per-call pricing

Fit

Best for

  • —AI agents needing programmatic cross-chain bridge route lookups
  • —Developers building multi-chain DeFi applications without managing multiple bridge API integrations
  • —Automated trading systems that need to move assets across chains

Not for

  • —Executing bridge transactions directly (this endpoint returns routes, not transaction execution)
  • —High-frequency use cases where per-call pricing at $0.02 adds up significantly
  • —Non-EVM chain bridging if the supported chain set doesn't cover your target

Quick start

# Using the x402-pay Python SDK
pip install x402-pay

import x402_pay
response = x402_pay.post(
  'https://defi.hugen.tokyo/defi/bridge/routes',
  json={
    "fromChain": "1",
    "toChain": "8453",
    "fromToken": "USDC",
    "toToken": "USDC",
    "fromAmount": "1000000000",
    "fromAddress": "0xYourWalletAddress"
  }
)

Example

Request

{
  "toChain": "8453",
  "toToken": "USDC",
  "fromChain": "1",
  "fromToken": "USDC",
  "fromAmount": "1000000000",
  "fromAddress": "0x1234567890abcdef1234567890abcdef12345678"
}

Response

{
  "routes": [
    {
      "id": "0x...",
      "steps": [],
      "gasCostUSD": "2.50"
    }
  ]
}

Endpoint

URLhttps://defi.hugen.tokyo/defi/bridge/routes
Transporthttp
Protocolx402
Pay to0x29322Ea7EcB34aA6164cb2ddeB9CE650902E4f60
CurrencyUSD COIN

Quality

0.62/ 1.00

The endpoint is live (402 challenge confirmed) and has an OpenAPI 3.1 spec, but the response schema for this specific endpoint is empty (no defined output shape). The request body schema is also not formally defined in the OpenAPI spec — parameters are inferred from the sibling /bridge/quote endpoint and the sample challenge response. No dedicated documentation page or examples beyond the stub in the 402 challenge.

Warnings

  • —Response schema is empty in the OpenAPI spec — actual response structure is not formally documented.
  • —Request body schema for the POST endpoint is not defined in the OpenAPI spec; parameters are inferred from the related /bridge/quote GET endpoint.
  • —The sample response in the 402 challenge shows an empty 'steps' array, so the full response shape is unclear.
  • —Root URL returns 404; no standalone documentation beyond the auto-generated /docs page.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 02:21:17Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/FVeqFy
Cross-chain bridge route discovery via x402 — find optimal bridging paths across EVM chains. — Clawmart · Clawmart