[ RPC · chain 34443 ]

mode, with proofs.

JSON-RPC for mode through one gateway over 2 measured endpoints. Every answer carries a receipt; a proved read adds the block proof under the superroot.

[ Endpoints ]

Call it now

curl -s https://coord.taifoon.dev/gw/rpc/34443 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

HTTPS: https://coord.taifoon.dev/gw/rpc/34443
methods: eth_blockNumber · eth_call · eth_getLogs · eth_getBlockBy* · eth_getTransaction* · eth_chainId · batch ≤ 20 · taifoon_getProof
health: healthy · 2 endpoints, 1 for logs read 2026-10-18 16:48 UTC
measured: best upstream 203 ms average, 240 ms p95, 99.9 % success · 2 active endpoints, archive available (the rotation's own probe, 2026-10-18 16:48 UTC) read 2026-10-18 16:48 UTC

Writes: transaction sends are being added through the streaming settle path; until then eth_sendRawTransaction is refused with a named reason. Limits and prices: below.

[ 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.

[ Data subscriptions ]

Stream what happens on mode

The producer follows this protocol on mode: layerzero_v2. Register a project scoped to the chain, then stream it or take its webhook.

curl -s -X POST https://coord.taifoon.dev/v1/projects -H "X-API-Key: $KEY" -H 'content-type: application/json' -d '{"id":"my-mode","name":"My mode watch","protocols":["layerzero_v2"],"filters":{"chains":[34443]}}'

curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-mode&from_seq=0" -H "X-API-Key: $KEY"

curl -s https://coord.taifoon.dev/v1/protocol/layerzero_v2/stuck

Protocol contracts the producer knows on mode: Across Protocol V3 DepositSource 0x3baD7AD0728f9917d1Bf08af5782dCbD516cDd96 · Across Protocol V3 FillTarget 0x3baD7AD0728f9917d1Bf08af5782dCbD516cDd96 · Relay.link DepositSource 0x4cd00e387622c35bddb9b4c962c136462338bc31 · Li.Fi / Jumper DepositSource 0x1231DEB6f5749EF6cE6943a275A1D3E7486F4EaE · Socket Gateway DepositSource 0x3a23F943181408EAC424116Af7b7790c94Cb97a5 · LayerZero V2 DepositSource 0x1a44076050125825900e736c501f859c50fE728c and 4 more.

[ Per-contract events ]

An event, as the lambda sees it

No order step on mode was in the boards at this read. read 2026-10-18 16:48 UTC

[ Proof streaming ]

Checked under the superroot

A proved read on any request: send x-taifoon-proof: 1 with the call, or taifoon_getProof.

[ 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-18 16:48 UTC

[ Partnership ]

Run mode with Taifoon

A chain or protocol team can claim the owner seat of its record: it then maintains its lanes and stage table, sets its pricing share, and the Conclave records the ownership and the share. Endpoint operators can add capacity to the rotation and earn per call.

curl -s https://coord.taifoon.dev/v1/owners/chain:34443

Claim: POST https://coord.taifoon.dev/v1/owners/chain:34443/claim with your key and a signature from an address your contracts name. Partner cards · add capacity.