Unichain, with proofs.
JSON-RPC for Unichain through one gateway over 0 measured endpoints. Every answer carries a receipt; a proved read adds the block proof under the superroot.
Call it now
curl -s https://coord.taifoon.dev/gw/rpc/130 -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'- HTTPS
- https://coord.taifoon.dev/gw/rpc/130
- 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.
Unichain: what you get, what it costs
- plain reads
- $0.50 per 1M · the lowest paid provider read: Tenderly Node RPC $39.00
- proved reads
- $5.00 per 1M · spinner does not collect this chain (chain_not_read)
- 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
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/mcpFirst call from any MCP client: tools/list, then taifoon_proof_tx with a chain and a transaction hash.
Stream what happens on Unichain
The producer follows this protocol on Unichain: u_demo_counter. 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-unichain","name":"My Unichain watch","protocols":["u_demo_counter"],"filters":{"chains":[130]}}'curl -N "https://coord.taifoon.dev/v1/pipe/stream?agents=my-unichain&from_seq=0" -H "X-API-Key: $KEY"curl -s https://coord.taifoon.dev/v1/protocol/u_demo_counter/stuckProtocol contracts the producer knows on Unichain: Across Protocol V3 DepositSource 0x09aea4b2242abC8bb4BB78D537A67a245A7bEC64 · Across Protocol V3 FillTarget 0x09aea4b2242abC8bb4BB78D537A67a245A7bEC64 · Mayan Finance (Swift) DepositSource 0x337685fdab40d39bd02028545a4ffa7d287cc3e2 · Mayan Finance (Swift) FillTarget 0xd78d199f8c402e7b5cc2abe278df0412400a3bae · Mayan Finance (Swift) SwiftDst 0x875d6d37ec55c8cf220b9e5080717549d8aa8eca · Relay.link DepositSource 0x4cd00e387622c35bddb9b4c962c136462338bc31 and 9 more.
An event, as the lambda sees it
No order step on Unichain was in the boards at this read. read 2026-10-17 00:52 UTC
Checked under the superroot
A proved read on any request: send x-taifoon-proof: 1 with the call, or taifoon_getProof.
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
Run Unichain 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:130Claim: POST https://coord.taifoon.dev/v1/owners/chain:130/claim with your key and a signature from an address your contracts name. Partner cards · add capacity.
