Guide · RPC

Use it as an RPC

Point a JSON-RPC client at the gateway, one URL per chain. Each call is recorded as a step with a receipt.

Send a call through the gateway

shell

curl -X POST https://coord.taifoon.dev/gw/rpc/8453 \
  -H 'content-type: application/json' -H 'X-API-Key: tfr_free_…' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

The answer is plain JSON-RPC:

answer

{ "jsonrpc": "2.0", "id": 1, "result": "0x31c1fff" }

The gateway serves reads only (eth_blockNumber, eth_call, eth_getLogs, blocks, transactions and receipts); a write such as eth_sendRawTransaction is refused with error -32003.

Caller	Allowance (MCP and RPC gateways together)
No key	100 calls a day
A free key	1,000 calls a day; take one with `POST /v1/register`
Past the allowance	A `402` with JSON-RPC error `-32402` that quotes the call over x402; prices are on /pricing

Take an endpoint instead

The layer keeps a rotation of public endpoints per chain, ranked by health. Ask for the best one and call it directly.

shell

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

The answer names best, best_logs (the best endpoint for eth_getLogs) and the ranked list.

Gas

shell

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

Base fee and priority-fee percentiles for the chain's latest block.