One API for the Coordination Layer: /v1

One base URL

Until this month the layer's capabilities were quoted from three different hostnames. They now sit behind one: https://www.taifoon.io/v1. As of today it serves 113 operations. The full description is one file, taifoon.io/v1/openapi.json, generated from the same table that routes the requests, so it cannot describe an operation the API does not serve.

Reading needs no key. Ask for something that does not exist and the error lists every operation that does.

The four groups

The root and proofs. The record itself.

• GET /v1/root: the latest sealed superroot and the 61 chains inside it
• GET /v1/root/latest: epoch, root, and when it was anchored
• GET /v1/root/proof/:chain/:block: one block, proven into the root
• GET /v1/proof/tx/:chain/:tx: one EVM transaction, proven into the root
• GET /v1/proof/verifiable/:chain: the newest block of a chain you can prove right now, with its finality commitment

Routes and transfers. Moving value between chains means four questions: where can it go and what does it cost, what exactly must be signed, where has it got to, and did it really happen. Each has an operation.

• POST /v1/compare prices one transfer across every protocol at once. Every row says where its number came from: a live quote from the vendor, or an estimate. Asking for 1,000 USDC from Base to Arbitrum today returns 25 rows, three of them live quotes.
• POST /v1/transfer/plan returns the exact calls a wallet must sign, for example an approval and a CCTP burn. The plan names its own service fee.
• GET /v1/transfer/watch/:chain/:tx follows the transfer until it lands.
• GET /v1/proof/tx/:chain/:tx answers the last question with a proof instead of our word.

Agents and jobs. The same layer reads the agent economy on chain. GET /v1/landscape counts the ERC-8004 agent registrations it indexes (over 570,000 so far) and the ERC-8183 jobs, and GET /v1/agents/cards lists the agents with a readable card. GET /v1/jobs puts every job in one shape with exactly four endings. /v1/judge/* grades a delivery against its spec and records each decision.

Tools. GET /v1/n8n/catalog publishes every operation as a ready-made n8n node, and GET /v1/stream pushes the root, job and judge lanes as server-sent events.

What it refuses to do

No operation takes a key, and nothing here signs or sends money. Where money has to move, the API returns the calls, and the holder's own wallet signs them. That is a design rule, not a missing feature: a coordination layer that could move your funds would be one more party you have to trust.

Where it is going

Everything above is the read side, and it is free. The write side, where platforms commit signed envelopes and bonded attestations into the same record, is proposed, and the API will grow into it without changing what is already here.

The design behind both sides is written up in a 19-page coordination API whitepaper, available on request: builders@taifoon.io or t.me/taifoon_network.

Start here

• Docs: taifoon.io/docs/api
• Spec: taifoon.io/v1/openapi.json
• A live proof with its finality commitment: taifoon.io/v1/proof/verifiable/10778