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
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:
{ "jsonrpc": "2.0", "id": 1, "result": "0x31c1fff" }The gateway serves reads (eth_blockNumber, eth_call, eth_getLogs, blocks, transactions and receipts) and relays eth_sendRawTransaction. Every other write or signing method (eth_sendTransaction, eth_sign, personal_sign) is refused with error -32003: the gateway holds no keys.
Send a signed transaction
Your wallet signs; the gateway relays the bytes. A wallet or cast pointed at the same URL sends as it would to any node:
cast send 0x0000000000000000000000000000000000000000 --value 0 --rpc-url https://coord.taifoon.dev/gw/rpc/36927 --private-key $YOUR_TEST_KEYThe answer is the transaction hash, or the node's own error (nonce too low, insufficient funds) with its code. Each send rides the coord pipe as a settle envelope signed by the gateway for provenance; the receipt is in the x-taifoon-receipt-pipe header (GET /v1/pipe/status/<envelope>), acked when the chain includes the transaction. The same bytes sent twice are relayed once. A batch of sends is relayed in order.
| Caller | Sends |
|---|---|
| No key | 20 transactions a day from one address |
| A key | 200 transactions a day free, then each request is a paid gateway call from the key's balance |
| Any caller | Signed for the chain of the URL (EIP-155), at most 128 KB; the node's answer within 8 s |
| 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, with a key | Paid from the key's balance: 0.50 USDC per 1M requests (a proved read 5.00 USDC per 1M). Top up with GET /v1/access/quote?usdc=1, then POST /v1/access/topup |
| Past the allowance, no key or no balance | A 402 with JSON-RPC error -32402 that names the free key and the top-up. No per-call x402 payment is taken on /gw/rpc; prices are on /plans |
Stream over WebSocket
The same chains answer on a WebSocket at wss://coord.taifoon.dev/gw/ws/{chainId}: eth_subscribe (newHeads, logs) and every read. Opening a connection is one gateway call on your key; the layer relays it to a rotation endpoint that first answered this chain's eth_chainId.
npx wscat -c 'wss://coord.taifoon.dev/gw/ws/42161' -H 'X-API-Key: tfr_free_…' -w 15 \
-x '{"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["newHeads"]}'The first message is the subscription id, then one message per new block. A browser WebSocket cannot set headers, so it sends the key as ?key=. Writes are refused per message with -32003. A connection lasts up to 60 minutes and 200,000 messages with a key (15 minutes and 2,000 without); then reconnect.
Archive chains
Moonbeam (1284), Moonriver (1285) and Moonbase Alpha (1287) no longer produce blocks. The gateway serves them as history at /gw/rpc/1284, /gw/rpc/1285 and /gw/rpc/1287, under the same allowance: 100 calls a day without a key, 1,000 a day with a free key, then from the key's balance. The head of such a chain does not move, and that is the correct answer. This is an independent service run by Taifoon, not an endpoint of the Moonbeam Foundation. GLMR and MOVR now live on Base: /gw/rpc/8453.
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.
curl https://coord.taifoon.dev/v1/rpc
curl https://coord.taifoon.dev/v1/rpc/8453The answer names best, best_logs (the best endpoint for eth_getLogs) and the ranked list.
Gas
curl https://coord.taifoon.dev/v1/gas/8453Base fee and priority-fee percentiles for the chain's latest block.