API · 3 of 5

Chains, RPC, gas and routes

The chains the layer reads, an RPC endpoint per chain, gas per chain, and what every way of moving value between two chains costs, priced at once.

THE COORDINATION LAYER · one namespace at https://coord.taifoon.dev/v1 · 8 operations on this page · machine-readable at /v1/openapi.json (see Reference)

Try it

The chains and the protocols that move value between them, an RPC endpoint ranked by health, and gas on Base.

curl https://coord.taifoon.dev/v1/chains
curl https://coord.taifoon.dev/v1/rpc/8453
curl https://coord.taifoon.dev/v1/gas/8453

Price 2 USDC from Base to Arc across every route at once. Amounts are in the token's smallest units.

curl -X POST https://coord.taifoon.dev/v1/compare \
  -H 'content-type: application/json' \
  -d '{"src_chain_id":8453,"dst_chain_id":5042,"dst_kind":"evm","asset":"USDC",
       "src_token":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
       "dst_token":"0x3600000000000000000000000000000000000000",
       "input_amount":"2000000"}'

Each row says how it was priced. source: "vendor" is the protocol's own quote; source: "synthetic" is an estimate from the protocol's fee model, not a price. When priced is false, a fee of 0 means unknown, not free.

The same route reads are served by the bridge gateway directly at https://arc.taifoon.dev/v1/ (v1/compare, v1/chains, v1/catalogue, v1/health). A browser calls them through the same-origin proxy /api/arc/, for example https://www.taifoon.io/api/arc/v1/chains. Filling a route spends solver funds and is not a public endpoint.

To send JSON-RPC calls through the layer, see Use it as an RPC.

Every operation (8)

Each row is generated from the table that routes /v1. The answer of each operation, field by field, is in the OpenAPI document; see Reference.