[ RPC · chain 1284 ]

Moonbeam, with proofs.

JSON-RPC for Moonbeam through one gateway over 0 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/1284 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

HTTPS: https://coord.taifoon.dev/gw/rpc/1284
methods: eth_blockNumber · eth_call · eth_getLogs · eth_getBlockBy* · eth_getTransaction* · eth_chainId · batch ≤ 20 · taifoon_getProof
health: healthy · 0 endpoints, 0 for logs read 2026-10-17 00:52 UTC
measured: unavailable at this read read 2026-10-17 00:52 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.

[ The card ]

Moonbeam: what you get, what it costs

plain reads: $0.50 per 1M
proved reads: $5.00 per 1M · no transaction in the last 8,000 blocks to test with
send relay: the same relay; no send verified on this chain yet
WebSocket: the WebSocket gateway answered 404 on both hosts on 2026-10-17: not listed until it answers
upstream: the warmbed rotation of public endpoints, failover per request
verified: 2026-10-17, with a free key

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

The producer follows this protocol on Moonbeam: 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-moonbeam","name":"My Moonbeam watch","protocols":["layerzero_v2"],"filters":{"chains":[1284]}}'

curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-moonbeam&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 Moonbeam: Li.Fi / Jumper DepositSource 0x1231DEB6f5749EF6cE6943a275A1D3E7486F4EaE · Squid Router DepositSource 0xce16F69375520ab01377ce7B88f5BA8C48F8D666 · LayerZero V2 DepositSource 0x1a44076050125825900e736c501f859c50fE728c · Hyperlane DepositSource 0xeA87ae93Fa0019a82A727bfd3eBd1cFCa8f64f1D · Synapse Bridge DepositSource 0x7e7a0e201fd38d3adaa9523da6c109a07118c96a · Synapse Bridge DepositSource 0xf07d1C752fAb503E47FEF309bf14fbDD3E867089 and 4 more.

[ Per-contract events ]

An event, as the lambda sees it

No order step on Moonbeam was in the boards at this read. read 2026-10-17 00:52 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-17 00:52 UTC

[ Partnership ]

Run Moonbeam 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:1284

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