[ Taifoon RPC ]

One gateway. Every answer with a receipt.

The same JSON-RPC methods on every chain at https://coord.taifoon.dev/gw/rpc/<chainId>, served over a measured rotation of endpoints. Ask for a proof and the answer carries the block proof under the superroot.

[ Chains ]

Pick a chain

Arbitrum One

chain 42161 · healthy · 6 endpoints

Arc

chain 5042 · healthy · 8 endpoints

Avalanche C-Chain

chain 43114 · healthy · 3 endpoints

Base

chain 8453 · healthy · 8 endpoints

BSC

chain 56 · healthy · 1 endpoints

Celo

chain 42220 · healthy · 4 endpoints

Ethereum

chain 1 · healthy · 8 endpoints

Optimism

chain 10 · healthy · 5 endpoints

Polygon

chain 137 · healthy · 3 endpoints

Robinhood Chain

chain 4663 · healthy · 4 endpoints

Taifoon devnet

chain 36927 · healthy · 1 endpoints

Taifoon mainnet

chain 3692781 · healthy · 1 endpoints

read 2026-10-16 15:44 UTC

[ Agents ]

Quick MCP

Connect an agent to the layer in one line. The MCP server answers without a key; its taifoon_register tool issues one.

claude mcp add --transport http taifoon https://coord.taifoon.dev/mcp

First call from any MCP client: tools/list, then taifoon_proof_tx with a chain and a transaction hash.

[ Beyond RPC ]

Streams, proofs and the coord API

Protocol events on these chains are streamed as typed envelopes (projects, webhooks, replay from a sequence number), each step proven under the superroot. The API catalogue:

curl -s "https://coord.taifoon.dev/v1/ops/search?q=stream"

API overview · project boards · CLI

[ Pricing ]

Free to start, metered after

unit	free a day (key / visitor)	USDC per 1M	GRID per 1M
one JSON-RPC request (a batch of up to 20 calls is one request)	1000 / 100	0.500000	25
one request that returns a block proof (taifoon_getProof, or any request sent with x-taifoon-proof: 1)	0 / 0	5.000000	250

One key and one balance for every product. Plans and top-ups: pricing. read 2026-10-16 15:44 UTC