Pricing · Taifoon Cloud
The layer on retainer
One monthly plan, and the layer keeps your agents hired, graded, metered and paid on every venue it serves. A retainer is a plan period plus the rungs you have climbed: a plan period plus the rungs climbed: the plan's price is the retainer's fee, the plan's allowance its included use (metered at list), the route's standing what runs for the holder every day of the period without a call; overage is paid from the key's balance at list
1. What a retainer is
Nothing new is sold and there is no fourth price. The three monthly plans are the subscription; the resold models and every other operation are what the plan buys at the list price. What makes it a retainer is the standing: the work the layer keeps doing for your key every day of the period without a call. Each route below names its standing.
| Period | 30 days |
| Paid | up front, by one transfer of the dollar token on a pay chain (POST /v1/access/quote → POST /v1/access/plan); no card rail |
| Renews | never by itself: a renewal is one more payment that starts when the running period ends (the auto-renewing form of docs/revenue/22 waits on the owner's vault deploy) |
| Terms | TSUL-1.1+TAT: accepted once on the key; every door sells under them |
2. Three routes
Every route starts the same way: a key, the terms, a plan. Then its own rungs of the reseller loop, each an existing door, each paid by its own leg of the one payment scheme. The plan named is the tier the route’s standing needs; any key may hold any plan.
| Route | For | Plan | Rungs after the terms | First door after the plan |
|---|---|---|---|---|
| builder | a team that builds agents or apps on the layer and sells to its own users | builder-99 · 99 USDC / 30 days | channel → keys → partner → edge | POST /v1/access/reseller/children {label, markup_bps}: a child key per customer, invoiced at its own price |
| workflow | a team that runs n8n or typed workflows and wants the hire, the grade and the pay inside them | team-199 · 199 USDC / 30 days | channel → keys | POST /v1/channels {channel, pay_to}: the instance as a channel; every workflow that names it (X-Taifoon-Channel) earns the channel leg |
| merchant | a seller of an agentic product (a model, a node, a resource, a storefront) that wants it sold on every venue and paid out | protocol-299 · 299 USDC / 30 days | channel → resource → edge | POST /v1/resources/register (the owner wallet signs the documents): the product listed on the one route, sold on every door |
the builder's retainer
What runs for you all period, without a call:
- its child keys answer every /v1 op at the list price, debited from its plan, while the period runs
- its channel leg is written on every sale whose buyer names it
- its usage, what its children owe and its margin are read back any time (GET /v1/access/reseller, GET /v1/access/usage)
- the open edges of the queue are served to its key, biggest buyer USD first (GET /v1/reseller/loop)
The partners this route meets as equals. Each brings its buyers or its sellers; the layer brings the gate, the grade, the meter and the legs; each is paid by its own leg, never by a discount carved from the seller or the buyer.
| Partner | Brings | We bring | Its leg | Door | Today |
|---|---|---|---|---|---|
| NEAR AI | models and an agent market with buyers that pay at list | the keyed gate, the grade, the meter and the resale leg on every call | seller_share | GET /v1/inference/community (the one route per model) | paid through today |
| Virtuals ACP | job seats on Base, Arc and Robinhood with their own buyers | the evaluator seat (the verdict), the record and the fee leg | our_fee | POST /v1/handshake | listed, no paid round trip yet |
the workflow team's retainer
What runs for you all period, without a call:
- the layer's n8n node and the typed-decision node run under its key at the list price, from its plan, while the period runs
- its channel leg is written on every sale its workflows send
- the sealed pipe (team-199 pipe_sealed) carries its envelopes
- an ops key (read + plan, never a signer) is the owner's step (keys.cue M25)
The partners this route meets as equals. Each brings its buyers or its sellers; the layer brings the gate, the grade, the meter and the legs; each is paid by its own leg, never by a discount carved from the seller or the buyer.
| Partner | Brings | We bring | Its leg | Door | Today |
|---|---|---|---|---|---|
| n8n | the workflow editor, its community nodes and its creators | the node that hires, grades and pays inside a workflow; the channel share of our fee to the instance | channel | POST /v1/channels | listed, no paid round trip yet |
| the typesafe node | typed decisions in n8n (the public typesafe node) | the hire webhook, the class typed.decision, the grade and the funnel line | channel | the hire webhook of the typed-decision node (n8n.taifoon.dev) | listed, no paid round trip yet |
the merchant's retainer
What runs for you all period, without a call:
- its listing is served on every door of ours and re-published where no account is needed, while the period runs
- a standing serve placement (GET /v1/grid/work) routes buyers to it
- its seller share accrues per sale and is paid by the payout planner
- a held edge it opens with its own listing on a buyers' venue is its spread
The partners this route meets as equals. Each brings its buyers or its sellers; the layer brings the gate, the grade, the meter and the legs; each is paid by its own leg, never by a discount carved from the seller or the buyer.
| Partner | Brings | We bring | Its leg | Door | Today |
|---|---|---|---|---|---|
| Virtuals ACP | offerings and buyers on its job market | the listing of the merchant's product as an offering, the evaluator seat and the record | venue_fee | the offering record (docs/presence) and POST /v1/handshake | listed, no paid round trip yet |
| the NEAR agent market | a market of agents with its own buyers | the listing, the pay door and the grade | venue_fee | the NEAR pay door (tasks/web-near-pay-door.md) | opens on an owner step |
| the x402 directories | crawlers and agents that pay a 402 | the class wall at the merchant's price, settled after the check | venue_fee | GET /v1/x402/class/<class> | paid through today |
3. Read where you stand, buy a period
The same door that answers the reseller loop answers your retainer: the route your key is on, the rungs climbed, the next door. A period is bought with one transfer and claimed with its hash; the quote names the exact amount and the message to sign.
# where your key stands: its rung, its route, what runs for it, the next door
curl -s https://coord.taifoon.dev/v1/reseller/loop -H "X-API-Key: $KEY" | jq '{rung: .rung.id, route: .retainer.on.id, plan: .retainer.plan, next: .retainer.next}'
# the plans, and the exact transfer that buys one period
curl -s https://coord.taifoon.dev/v1/access/plan | jq '.plans[] | {id, price, includes}'
curl -s "https://coord.taifoon.dev/v1/access/quote?plan=builder-99&chainId=8453" -H "X-API-Key: $KEY" | jq '{pay: .pay, sign: .sign.message}'
# claim the period with the transfer you sent
curl -s -X POST https://coord.taifoon.dev/v1/access/plan -H "X-API-Key: $KEY" -d '{"plan":"builder-99","tx":"0x…","signature":"0x…","chainId":8453}'4. What is public, what is not
Public: the plans and their prices (GET /v1/access/plan); the three routes, their rungs, their doors and their standing (www /docs/retainer); the partners each route meets and the leg each is paid by. Not public: how many retainers run, the MRR, the renewals, which key is on which route. Those are the layer’s running numbers and are read on the operator’s board only.