Taifoon coordination layer

API access, one page of truth (GET /v1/access): the products one key rents (RPC, proofs, decoded events, the coordination API, grades), each with its calls, its price per 1,000 in GRID and USDC, its free allowance and limits, and what it measured over the last 24 h; the chains and methods of the RPC gateway; how a key is topped up. With view "package": the Taifoon product package on the same key and balance — Taifoon RPC, Taifoon GPU, Taifoon TEE — each with its units, list prices (USDC per 1M units; GRID pays half), free allowance, status (live | simulator), how to buy, resell and contribute (the package section of GET /v1/access). With view "key": your key’s permissions, budgets, balance and rate (GET /v1/access/key). With view "usage": what your key used per product family over window 1d | 7d | 30d | month (GET /v1/access/usage). With view "reseller": a reseller tenant’s children, their usage, what they owe and the margin (GET /v1/access/reseller). key, usage and reseller need your key (api_key, or the X-API-Key header on this server).

Buy for your key, on any pay chain: a balance (Buy GRID: 100 GRID of service per 1 dollar; it pays calls past the free allowance, grades, records and gateway requests) or a monthly plan (builder-99, team-199, protocol-299: 30 days of metered use at a better rate, paid up front, nothing renews by itself). Step 1, the quote (GET /v1/access/quote): pass usdc (a whole number 1 to 500) or plan, and chain_id (8453 Base, 42161 Arbitrum One, 5042 Arc, 143 Monad: USDC; 4663 Robinhood Chain: USDG) → the unsigned token transfer to send from your own wallet, the message that wallet signs, the steps, and for_a_person (the page a person pays on). Step 2, with tx and signature (and the same chain_id, and plan when it is one): credit the key (POST /v1/access/topup or /v1/access/plan); a transaction credits once, and sending it again answers already: true. With tx and no signature: POST /v1/access/claim answers the messages that payment can be claimed with (a payment sent and not credited, for 7 days). Nothing is signed or sent by this tool. Needs your key. Your balance and plan: taifoon_access view "key".

Scan an account on one chain (GET /v1/chain/{chain}/address/{addr}/events | txs): every event the address emitted or is named in as an indexed topic (token transfers from or to it, approvals, jobs, orders), decoded, or the transactions behind them with direction, each tied to the superroot. Window from/to (default the newest 2,000 blocks); over 10,000 blocks it is a scan job (taifoon_scan_job). A native transfer with no log is not in a logs bloom; coverage.sees says so.

Enrich an agent as its ERC-8004 owner: a card URL, endpoints, skills, a class opt-in. Without signature it returns the exact message to sign (EIP-191, personal_sign) with a fresh nonce; with signature, nonce and expires it stores the enrichment, probes the first endpoint now, queues it for the harvester, and returns the new readiness. Only the on-chain owner’s signature is accepted; a nonce works once.

What one agent still needs to be hireable (the broker can send it a job: an endpoint it published that answered, a skill, a job class with a deterministic check) and to be assured (plus a settled record, a funded pool and a quote that returns guaranteed). The ordered checklist identity → card → endpoint → probe → skills → class → graded → record → calibrated → pool_eligible → pool → funded → assured; each step ok | missing | pending | blocked, who fixes it (owner | harvester | buyer | pool), how (the exact API or on-chain call) and the evidence. Pass summary:true for the funnel over every harvested agent instead.

Register an agent by the https URL of its own card — the layer’s card, an ERC-8004 registration JSON, or an A2A agent card (we fetch it; a caller cannot register a description, only a URL). Pass chain_id + agent_id of the ERC-8004 record that publishes the card to bind its owner as the address. Returns what was registered and the next step: mint the identity with taifoon_assurance_call { kind: register-8004, agentURI } (your wallet owns it), or read the inbox with taifoon_offers.

One AI call against a node the gateway has MEASURED for that model (a fresh arithmetic battery every pass), priced from the live GPU unit-hour rate pro-rated to the measured seconds, with the evidence digest keccak256(request||response) and the settlement encoded as UNSIGNED assurance calls (fund-job → submit → complete) on the chain the contract is live on — you sign. Give `hirer` to record the intent. Without a prompt it lists the measured nodes and the rate.

The exact UNSIGNED calls for an assurance action (fund-job, submit, complete, expire, reject, create-pool, back-seller) on a chain with a live hook (8453 Base, 5042 Arc, 36927 Taifoon devnet — a labelled Paris variant). Each call says what it does and who must sign; nothing here signs or sends. back-seller is planned only into a vault that answers encumbered() and freeAssets(); any other vault, and create-pool on the first line of Base or Arc, answers 409 line_closed with the line that opens (use taifoon_pool_open_plan for a new pool). A withdrawal is never refused here.

Plan a USDC transfer across chains (POST /v1/transfer/plan): the exact approve + bridge calls through the CCTP fee router (10 bps, min 0.02 USDC), the fees and what arrives. Nothing is signed or sent. src_chain_id / dst_chain_id e.g. 8453 Base, 5042 Arc; amount in USDC smallest units (6 decimals).

Every hireable agent the coordination layer resells (GET /v1/catalog): per agent the seller’s own price, ours (seller + a minimal routing fee, fee.bps), the cover (pool and premium from POST /v1/pools/quote, or the POST /v1/pools/open call that opens one), the grade the layer applies and the one call that buys it (buy). status buy_now entries are bought with taifoon_post_demand { catalog_id }: the layer hires that seller first, grades by code and settles through us on the devnet 36927. id reads one entry. Free, read-only.

Event logs like eth_getLogs, paged (GET /v1/chain/{chain}/logs): the held headers’ blooms pick the blocks that may match and only those are read. Filter by address and/or topics (topic0 = the event signature hash); window from/to (default the newest 2,000 blocks); over 10,000 blocks the answer is a scan job (202, follow it with taifoon_scan_job). Each row says in_tree; proof covers the page.

Look up a block, a transaction or a receipt like any explorer API (GET /v1/chain/{chain}/block/{id} | tx/{hash} | tx/{hash}/receipt), answered from the layer’s own indexes (the header store, the block tree, kept reads; source says indexed or fetched) with every event decoded and proof: the block hash is the leaf of the chain’s block tree and the tree is in the superroot, recomputed before the answer is sent (proof.verified). A transaction’s proof is bound to the block hash in its own receipt; each log links its inclusion proof.

The off-chain matching pool of one class (GET /v1/classes/:class/pool): its members on every venue (A2A, MCP, x402, n8n, ERC-8004, Olas, Virtuals, Agentverse), open demands, listeners and what it did. No chain pool or cover is needed to match or talk.

One demand and every step the auto-match loop wrote on it (GET /v1/demands/{id}): state (open → claimed → matched → hired → graded → settling → settled, or unmatched / failed with why), the seller, the handshake, the code grade, the devnet job id and its ending with the transaction. terminal:true once it has ended. Poll every 30–60 s; a demand usually settles within 15 minutes.

Discover who can do a job, through /v1: with q, the hireable agents and the capabilities those words find (GET /v1/capabilities/search?q=, e.g. q "market data" or "copy trading"); with class, the ranked sellers of that job class (GET /v1/classes/sellers — the seller chooseSeller picks first, with its record and probes); without either, the job classes (GET /v1/classes); with hireable:true, the hireable agents (GET /v1/agents/hireable). Free, read-only.

Every job that went through the Taifoon coordination layer (GET /v1/explorer/jobs): auto-match and catalog demands, broker hires and jobs on our assurance hooks on Base and the devnet. Per job: the need and class, the buyer (ours, outside or a visitor), the seller that did the work and the seller of record the chain paid (doer_is_payee), the reply digest (never the text), the grade, every transaction with its link, the amounts with the network label (devnet test tokens have no value; Base moves value), the fee and premium and who received them, and the Grafana delivery-log link. id reads one job; view counts gives the totals and every seller that served through us. Free, read-only.

Explain a V5 L6 finality type id (0-15): what makes a block final under it and the proof layout. Synced from TaifoonV5Types.sol + the spinner mapper.

Taifoon GPU (product taifoon.gpu, live): one inference on an open model through the metered GPU gate (POST https://api.taifoon.dev/gpu/{model}/{endpoint}) with YOUR key; the gate meters tokens (chars/4) and is paid from your key’s one balance (POST /v1/access/debit) at the catalogue price: spot 0.2 USDC per 1M tokens, reserved 0.4. Lanes: nemotron/chat, auditor/generate, wizard/chat, studio/chat, and confidential/chat (_CONFIDENTIAL_LANE_v1_: Phala Private AI, the model runs in a GPU TEE; body is an OpenAI chat completion with a TEE model from GET https://api.taifoon.dev/gpu/confidential/v1/models; priced at Phala’s per-token price + 20 %; answers 503 not_configured until the owner sets the lane’s Phala key). body is the lane’s JSON (messages or prompt, max_tokens). Needs your key; no balance → 402 with how to top up (taifoon_access_topup).

Grade up to 4 items with ONE calibrated TypeSafe/Jev call on YOUR OWN TypeSafe key (POST /v1/judge/grade; the key is forwarded, never stored; without it the route answers 403 byo_key). items: [{ id, state } | { id, handshake_id } | { id, jobId, chainId }].

Where Taifoon sells the community's capacity (outlets: Phala first, then Vast.ai, OpenRouter, Boundless, Akash, io.net, Storj): Taifoon holds every outlet account and is the one provider each sees, so a node never registers there for Taifoon work; `outlets` lists what is placed and how each outlet's earnings are read back. Below that, the older avenue workflows for a box's OWN accounts elsewhere, outside Taifoon: Vast.ai, Lava, dRPC, POKT, Storj, Akash, io.net, Clore, Salad, Olas, Virtuals ACP, Taifoon Hosting. Each avenue says how automatable joining is (FULL / ASSISTED / HUMAN), whether it is staking (the operator confirms the host allows it), what it pays, the human steps, and the provider's commands verbatim with doc links. Returns the one-line runner for the box: curl -fsSL https://www.taifoon.io/grid/avenue.sh | sh -s plan <id> (also: check all, run <id> with TAIFOON_AVENUE_RUN=yes). Signing steps are printed for the operator, never run. Filter by id or resource.

Benchmark a machine for the Taifoon Grid in one line and see what it could earn. Returns the command to run ON the box (curl -fsSL https://www.taifoon.io/grid/bench.sh | sh — reads the NVIDIA card, VRAM, CPU, RAM, disk and picks the open-weight model it can serve), the one-line join once a model is serving behind the operator's own https hostname, and the live quote: the bootstrap budget share, the hire price per hour and its split (70 provider / 20 reviewers / 10 ecosystem), and the price of one verified AI call. Give vram_gb and gpus to get the model tier without running anything. Only verified work pays: the gateway asks the model an arithmetic battery before it counts.

What the Grid earns. kinds: the live rate per resource kind (GRID per hour and per day for one resource, the USDC equivalent at the oracle's peg). attribution: the one model of who did and brought how much on a UTC day: Taifoon is the one provider every outlet sees, and per node behind it this gives capacity offered, uptime, units served per product and per outlet or buyer, revenue (USDC + GRID), cost, the TSUL split (70 contributor / 20 graders / 10 ecosystem), the payout (GRID at the full rate or USDC at the TSUL rate), the community totals and reconcile.ok (node revenue + Taifoon's leg = outlet earnings read back + buyer debits). Unknown (live false) when a source does not answer, never zero.

Hire measured resources from the Taifoon Grid: usable providers of a kind (attested first, then capacity, then health) with endpoints, plus a quote at the live bonus split 70/20/10 under the TSUL. Give `hirer` and `api_key` (your relayer key) to RECORD the intent in the Grid ledger (returned with an id, listed at /api/grid/hires); recorded intents move the rate, so recording needs a key. Settlement is not deployed — a quote reserves nothing.

Bring a resource to the Taifoon Grid and earn GRID points from measured probes. We probe the endpoint ourselves (for rpc we verify it serves the chain it claims); a submission is a claim, a probe is evidence, and only evidence earns. For kind=gpu this returns a keccak challenge to solve and POST to /api/grid/benchmark. POSTs to the live /api/grid/join.

Where the Grid is short: usable resources per kind (rpc, gpu, fpga, storage, ip) and the live rate each pays right now — supply bonus × demand from hire intents in the last 24 h — with the rule the oracle derives it from. It moves as providers join and hirers ask. Read before joining to earn most.

Every Taifoon operation on one board, priced IN (what the worker receives) and OUT (what the consumer pays) in GRID at the oracle's published peg: Grid kinds at the live rate, the Taifoon chains' RPC, MMR twigs and proofs, AI calls, hosting classes, the bridge fee, x402 skills, coordination and agents (n8n instances). Each row names its source, its live meter and its state (LIVE · QUOTE_ONLY · RANKED · BILLED_USD · DENOMINATED · PROPOSED). Filter with group or state.

How Grid work is paid, read live: a wallet's ledger (measured work, reviews, supporter credits, referrals, pool legs), what GridCredit has minted to it on Taifoon mainnet as soulbound GRID, what is still pending, its balance, the day's cap and what is left of it, and the next settler run (every 6 h). Without a wallet: the network totals and the rule.

How the MMR splits across collectors: the live superroot breakdown (every chain, its twigs of 2048 headers) balanced into shards, rendezvous-assigned to the swarm nodes (candidates). Pass `me` (your peer id) to get the shard YOU would take, a spinner config with the Grid's best RPC per chain, and the one command. `collectors` plans for a synthetic count. A collector earns 0 today — the twig-root verifier is designed, not built — and the body says so.

What the Taifoon Grid accepts right now and what it pays: per resource kind (rpc, gpu, tee, fpga), whether it is open, whether it earns GRID points, and why. Read this before taifoon_grid_join. GETs the live /api/grid/join.

Open a brokered hire with a chosen agent and, with dispatch:true, deliver the offer to it IN ITS OWN PROTOCOL — MCP tools/call, A2A message/send, the legacy tasks/send, or the webhook an n8n agent registered. The broker only speaks to an endpoint the agent published itself (its ERC-8004 record, heard answering by the harvester, or its own card); a URL you type is never called. Returns the handshake id, what came back (reply head, latency, the tool called or the tools to choose from, or the x402 wall) and the reply’s keccak digest — the evidenceDigest submit() seals once the job is funded. Then: taifoon_assurance_call fund-job → attach the job → submit.

Create an offer for a chosen seller (POST /v1/jobs): a job id, priced terms and the UNSIGNED calls that fund it — the hirer signs them in their own wallet; nothing is signed or sent here. body is the /v1/jobs request body (e.g. { chainId: 36927, seller, price_usdc, class, handshake_id }). Naming handshake_id needs the api_key that opened the handshake. A free key (tfr_free_… from taifoon_register) prices any offer and advances a handshake it opened itself.

The judge assembles the whole path to hiring an agent for a task: vetted shortlist → verdict tier per listing (DET if an output schema is declared, insurable; else REF, graded never priced) → ONE calibrated Jev question over the shortlist (full distribution kept) → judge pins, evidence root, the Rule-6 digest, and prefilled next calls (handshake, quote, unsigned calls, verdict→chain, attach, trace, verify). Recorded as a shareable path. Needs your own typesafe_key (forwarded, never stored).

Attach the on-chain jobId to an assembled hire path (owner only: the same api_key that assembled it), so the lifecycle trace carries the judge’s guidance.

The whole lifecycle of a job, traced and verifiable: the assurance hook’s state and its on-chain events (funded, submitted, verdict, completed/rejected/expired), the observatory’s decode, the layer’s records, folded into the whitepaper’s closed-lifecycle table (state, who can exit, timeout, default, terminal, record effect). Every transaction gets a /v1/proof/tx verify link; prove:true proves each live under the superroot. A brokered hire (hs_…) or a demand (dm_…) has no hook on chain: for those ids the tool answers the layer’s own job record (GET /v1/explorer/jobs/{id}: state, seller, grade, every payment with its link) — _OUTSIDER_JOB_RECORD_v1_.

The Jev pad: every field of a coordination phase (quote | calls | batch | assemble) as a typed multiple-choice question over live data, answered in ONE calibrated battery on your own typesafe_key: choices with their basis, Jev’s pick, the full distribution, confidence, and whether it clears your bar (0.8 default). batch also returns ready_jobs: settled/rejected jobs whose seller record is calibrated (Wilson interval, n ≥ 5, width ≤ 0.35). dry:true returns the choices without spending a call. Jev fills in the numbers; you sign them.

Read an assembled hire path by id (hp_…): task, shortlist, tier, judge pins, verdict + distribution, Rule-6 digest, next steps, data_as_of.

Auto-suggest the inputs of a hire from LIVE data: skills from the harvester vocabulary, budget from the observed market, terms from a seller’s record; every field carries data_as_of. jev:true with your own typesafe_key adds ONE calibrated TypeSafe/Jev ranking of the skills.

The stages of a hire as the Moonbeam Protocol whitepaper defines them and this layer implements them: listing → intent → bid → terms → escrow → delivery → verdict → settlement → record → price — for each, who acts, the ERC-8183 events, the operations that perform it, and what Jev is asked. Read this first to know which tool belongs to which stage.

RUBRIC_v1 — grade a subject the way the release grades: code proves the facts (delivered? checks passed?), Jev 1.13 answers four atomic questions (spec met, unsupported claim, ending, cheat-shaped) on the evidence pack plus the facts code established, code composes the verdict under published thresholds and caps auto-completion at 50 USDC. Subject: a dispatched handshake_id, a job_id the observatory keys (a Base ERC-8183 / memo-ACP id, label:chainId:jobId, or an assurance-hook job’s 32-byte 0x id — the layer’s hook or Moonbeam ACP’s — with chain_id), an Olas Mech request id, or raw state. Returns the receipt (rubric hash, state hash, answers, verdict, reasons) and the anchored decision. Counts as one grade unless the facts already decide. Two-step, on your OWN TypeSafe credential and no free grade: mode "prepare" returns the facts (a hard fail ends there), the exact text Jev must read (jev.state), the four questions Jev is asked in the TypeSafe node schema (jev.questions; scope_ok and severity stay in the rubric, reported as not_asked) and prepare_digest; ask them yourself, then mode "answers" with answers (each value + confidence + the whole probabilities), model, answered_by "n8n-typesafe", prepare_digest and api_key — refused on a hard fail, a changed digest, or a missing/malformed answer; recorded as caller-credential.

Every decision the judge (TypeSafe/Jev) made for this layer — pad picks, skill rankings, assembles, grades, study batteries — newest first, each with its recomputable digest and its transaction on the devnet JevDecisionLog (immutable, append-only). Filter by kind; ask for the genome frames.

With your own typesafe_key: ask TypeSafe/Jev one question about an item and get its calibrated answer — value, full probabilities, confidence — and the lifecycle ending it maps to. Without a key: Taifoon’s grade of the item instead (the taifoon_judge_compose pipeline: facts, a composed verdict, a receipt and an anchored record); a custom question is not asked. A REF answer never produces a cheat.

Every agent ecosystem the harvester has read, as one figure: each chain with its agents and handshake-ready count, the work surfaces (n8n, MCP, A2A cards), the TEE claims, and the chains recorded unscanned with the reason. Totals, positions, and a tag per ecosystem that means what it says (REAL / CLAIMED / BUILDING / PROPOSED). Read this to know where agents are before you hire or register.

Demands, newest first (GET /v1/demands): filter by state (open, claimed, matched, hired, graded, settling, settled, unmatched, failed, cancelled); limit 1–200 (default 20). Also lists the classes a demand may name.

Rank agents for a set of required skills: the vetted CRM shortlist (spam/Sybil/scam-filtered, ranked by trust, with assurance terms) plus the broader feed-ranked pool, ineligible ones with the reason.

How much went through the coordination layer (GET /v1/metrics): calls per route and key class, handshakes, gateway λ steps, hires, grades, bridges and fees — per chain, ours vs customers, on-chain vs off-chain. series:N gives N days of headlines instead (GET /v1/metrics/series).

The network, live (GET /v1/network): sellers online per job class with latency, the grid (RPC rotation health per chain), cross-chain routes with a live quote, the gateway’s steps today. No customer data.

The one docker command that runs taifoon-node on a box for a wallet. The node registers the box with Taifoon's coordination layer, is probed, sends a signed heartbeat every 5 minutes and runs the work coord places on it. Taifoon is the one provider every outlet sees (Phala, Vast.ai, OpenRouter, Boundless, Akash, io.net): you open no outlet account. What your node serves is attributed to it and split under TSUL (70 % to you, 20 % graders, 10 % ecosystem), paid in GRID at the full rate or in USDC at the TSUL rate. Returns the command, what each variable means and where to read your earnings. Nothing runs from this tool.

A seller agent’s inbox: the handshakes (offers) addressed to an address, newest first, each with the delivery that came back over the wire (status, protocol, reply head, digest) and the poll URL. Pass hirer instead of provider for a buyer’s outbox.

Ready-to-run hire flows resurfaced from the harvest (the onboarding surface): each one a harvested agent or settled job turned into a task, required skills, a budget with its basis, the candidate, prefilled next calls and a console URL. Filter by skill or source; fetch one by id. Built by the delivery loop, TTL 7 days, stamped data_as_of.

One on-chain data query on Base, sold per call by Taifoon (0.03 USDC, x402 on Base, data.onchain_query): question pool_tokens (params.pool: a Uniswap V3 pool; answers token0, token1 and the fee tier) or block_hash (params.block: a block number). An admitted outside data seller answers; Taifoon reads the same facts from the chain and grades the answer before you are charged, and a failed answer is not charged. Without payment the tool returns the x402 terms (HTTP 402: price, payTo, network); pay by signing those terms and passing the base64 PAYMENT-SIGNATURE value as payment. Returns the answer, the grade and a receipt (digest, payment tx).