TAPEAPI 3.0 · v3.0.0 · 2026-11-06 · BNB 56 · X LAYER 196 · BASE 8453
一次 AI 调用留下签名回执；一个 Agent 的身份和花钱规则，别人在自己的机器上就能重新查一遍。不用先认识它，不用相信它自己怎么说。
An AI call leaves a signed receipt. An agent's identity and its spending rules can be checked again by anyone, on their own machine. You need not know it first, and you need not take its word.
UNAVAILABLE
两家运营方读到的不一致，所以结果是「不知道」，不猜。
The two operators read different answers, so the result is "unknown". It does not guess.
读不一致就说不知道，是这套机制最重要的一条。
Saying "unknown" when the reads disagree is the most important rule in this mechanism.
四层，都能自己查
Four layers, each one checkable by you
同一钉块、两家以上运营方一致，才说这个 ERC-8004 身份和这枚 TapeOut 电路是同一个钱包持有。
Only when two or more operators agree at one pinned block does it say that one wallet holds this ERC-8004 identity and this TapeOut circuit.
tapeapi passport <名字name>
MCP 工具定义的哈希钉在链上，也钉在你本机。之后定义变了，就拒绝这个服务。
The hash of an MCP server's tool definitions is pinned on chain and on your machine. If the definitions change later, that service is refused.
tapeapi-mcp
回执和账单逐行对；3.0 加按服务、模型、天汇总的清单，和发出前拦住超额的本地预算。
Receipts are set against a bill row by row. 3.0 adds a statement by service, model and day, and a local budget that stops an over-limit call before it is sent.
tapeapi reconcile
委托人的花钱规则写成小电路，对方自己重跑；没电路、哈希不对、已撤销，一律拒绝。
The principal's spending rule is written as a small circuit that the other side re-runs. No circuit, a wrong hash, or a revoked binding: denied.
admit()
回执长什么样
What a receipt looks like
AI 用量回执的结构取自 TAPI-21 规范，数值为示例。
The structure of an AI usage receipt comes from the TAPI-21 spec; the values are examples.
{ "id": "chatcmpl-v1", "ok": true,
"container": "0x…", 1
"ts": 1790000000,
"method": "openai_chat",
"params": { "path": "/v1/chat/completions",
"requestSha256": "<64 hex>" }, 2
"result": {
"model": "gpt-x", 5
"usage": { "prompt_tokens": 1200, "completion_tokens": 300,
"total_tokens": 1500, "cache_read_tokens": 1000,
"reasoning_tokens": 100 }, 4
"responseSha256": "<64 hex>", 3
"stream": false, "complete": true, "status": 200,
"prices": [ { "currency": "USDT", "amount": "0.00357500" },
{ "currency": "BEM", "amount": "0.03375000" } ], 4
"modelMatchedBy": "response" },
"sig": "0x…" } 1container 与 sig：谁签的。签名能恢复出签名者，它必须是电路持有人在链上委托的密钥。container and sig: who signed. The signature recovers the signer, which must be a key the circuit's holder delegated on chain.params.requestSha256：答的是哪个请求。你发出的字节的哈希，由你的 SDK 对照。params.requestSha256: which request. The hash of the bytes you sent, compared by your SDK.result.responseSha256：回了哪些字节。result.responseSha256: which bytes came back.usage 与 prices：声称的用量，和按链上价目表算出的金额；任何人都能重算。价目表只是公开声明，不经结算，用户照旧向服务方付款。usage and prices: the claimed usage, and the amount from the on-chain price table; anyone can recompute it. The price table is a public statement, not settled: users pay the provider as before.model：只是上游报的名字。回执不证明实际跑的是哪个模型。model: only the name the upstream reported. A receipt does not prove which model actually ran.一张回执证明什么
What one receipt proves
| 问题Question | 回执里的依据Evidence in the receipt | 证明Proven |
|---|---|---|
| 谁回答的Who answered | 持有人在链上委托的签名密钥A signing key the holder delegated on chain | 1 |
| 回答的是哪个请求To which exact request | requestSha256 | 1 |
| 回答了哪些字节With which exact bytes | responseSha256 | 1 |
| 声称的用量与价格Claimed usage and price | token 数，按链上价目表重算的金额Token counts; an amount anyone recomputes from the on-chain table | 1 |
| 实际跑的是哪个模型Which model actually ran | model 只是上游自己报的名字model is only the name the upstream reported | 0 |
回执不证明实际跑的是哪个模型。服务方可以把便宜模型的回答标成贵的。签名带来的是可追责：回执无法抵赖，任何人发测试请求、公开结果，都会留下证据。
A receipt does not prove which model actually ran. A provider could label a cheaper model's answer as a dearer one. What the signature adds is accountability: a receipt cannot be disowned, so anyone sending test prompts and publishing the results leaves evidence.
接入方式
How it fits in
旁路会经手用户的 API 密钥，所以由服务方自己部署；TapeAPI 不托管。链上价目表只是公开声明，不经结算，用户照旧向服务方付款。支持 OpenAI Chat、Responses、Anthropic Messages 和 Embeddings，流式也支持。
The sidecar handles your users' API keys, so the provider runs it; TapeAPI never hosts it. The on-chain prices are a public statement, not settled: users pay the provider as before. OpenAI Chat, Responses, Anthropic Messages and Embeddings, streams included.
你是谁，从哪开始
Who you are, where to start
AI 服务方
AI providers
在 OpenAI 或 Anthropic 兼容接口前面放一个签名旁路，你的用户只改 base URL。
Put a signing sidecar in front of an OpenAI- or Anthropic-compatible API. Your users change only the base URL.
给 AI 服务方 →For AI providers →调用方
Callers
用 SDK 或 tapeapi-verify 对照链上记录，核验回执、对账、钉住 MCP 工具。
Use the SDK or tapeapi-verify to check receipts against the chain, reconcile bills and pin MCP tools.
Agent 与守门方
Agents and gatekeepers
护照查身份，策略电路重跑规则，本地预算拦住超额。3.0 新增，实验性。
The passport checks identity, a policy circuit re-runs the rule, a local budget stops overspend. New in 3.0, experimental.
Agent 护照 →Agent Passport →NEW IN 3.0
tapeapi passport、@tapeapi/passport。在同一个钉住的区块上读链，两家以上运营方一致才下结论：这个 ERC-8004 身份和这枚 TapeOut 电路，是不是同一个钱包持有；读不一致就说「不知道」。tapeapi passport, @tapeapi/passport. It reads the chain at one pinned block and concludes only when two or more operators agree: whether one wallet holds this ERC-8004 identity and this TapeOut circuit. When the reads disagree it says "unknown".@tapeapi/policy-circuit。花钱的规则写成小电路，对方自己重跑，拿不准就拒绝。@tapeapi/policy-circuit. A spending rule is written as a small circuit that the other side re-runs; when unsure, it denies.tapeapi receipts statement。按服务、模型、天汇总，并在调用发出之前拦住超额。tapeapi receipts statement. It sums spend by service, model and day, and stops an over-limit call before it is sent.限制，如实说
The limits, plainly
标准即默认。不传选项，SDK 就按 TapeOut 官方 TAP 解析服务：每次解析钉一个区块，链 ID 与持有人要所有节点一致，名字未开通或未付费就得到一个明确的状态，而不是悄悄解析成功。TAP-11 与 TAP-13 由我们起草，已合并为 Draft（合并不等于被采纳）。要 1.x 的行为，传 conform: false。
Standards by default. Pass no options and the SDK resolves a service as TapeOut's official TAPs say: one pinned block, all nodes agreeing on chain and owner, and a named status for a name not opened or not paid up. TAP-11 and TAP-13 to TAP-18, drafts we wrote, are merged as Drafts (a merge is not adoption). For 1.x: conform: false.
同一版首次公开三项实验性功能——有界代理、美元报价、容器间评价。它们依赖的托管合约未经审计、未部署，主网不可用，今天只在本地链与测试中可以验证，也不收任何费用。
The same release first makes public three experimental features: bounded agents, US-dollar prices and reviews between containers. The escrow they rely on is not audited and not deployed, so they do not work on mainnet; today they are checked on local chains and in tests only, and nothing is charged.
安装
Install
包还不在 npm 上，从 GitHub 发布页装进一个空目录。需要 Node.js 22 或更高版本。
The packages are not on npm yet; install them from the GitHub release into an empty directory. Node.js 22 or later is required.
npm install \ https://github.com/BruceLanLan/tapeapi/releases/download/v3.0.0/tapeapi-sdk-3.0.0.tgz \ https://github.com/BruceLanLan/tapeapi/releases/download/v3.0.0/tapeapi-server-3.0.0.tgz
A · curl向公共服务要 BNB 价格。curl 只显示签名信封，不做任何核对；验签用 SDK 或调试台。Ask the public service for the BNB price. curl shows the signed envelope and checks nothing; the SDK or the playground verifies it.
curl -s https://api.tapeapi.fun/tapeapi/v1/bnbUsd -H 'content-type: application/json' -d '{"id":"1","params":{}}'B · SDK存为 try.mjs，在装好 SDK 的目录里运行 node try.mjs：SDK 从链上解析服务、验签，验签成功才返回结果。Save this as try.mjs and run node try.mjs in the directory where the SDK is installed: the SDK resolves the service from the chain and verifies the answer before it returns.
import { createTapeAPI, rpcUrlsFor } from '@tapeapi/sdk' const api = createTapeAPI({ rpcUrls: rpcUrlsFor(56) }) // 3 家运营方的节点nodes of 3 operators const service = await api.resolve('11.1013.tape') // 按官方 TAP 解析resolved as the official TAPs say const { result, verified } = await api.call(service, 'bnbUsd', {}) console.log(result.bnbUsd, verified) // 验签成功才为 truetrue only after the signature checked out
现已上线
Live now
我们运行的 · 免费（付费托管合约未部署）· 无需注册
Run by us · free (the paid-call escrow is not deployed) · no sign-up
8 个签名读取，其中 7 个钉在一个区块上。公共 API 指南 →
Eight signed reads, seven of them pinned to one block. Public API guide →
同样 8 个方法，任何 MCP 客户端按网址添加。MCP 指南 →
The same eight methods, added by URL in any MCP client. MCP guide →
承载加密通道与群聊，只存密文。通道指南 →
Carries encrypted channels and groups, ciphertext only. Channels guide →
BNB Chain 上承载通道帧的合约，无所有者、不可升级。群聊指南 →
Carries channel frames on BNB Chain; no owner, not upgradeable. Groups guide →
由你自己部署或运行
Yours to run
四种格式，含流式；经手用户密钥，所以不托管。AI 服务方指南 →
Four formats, streams included; it handles your users' keys, so it is never hosted. Guide for AI providers →
tapeapi-verify本地核验代理，给读不到回执的客户端用。AI 服务方指南 →
A local proxy for clients that cannot read receipts. Guide for AI providers →
固定测试请求，只给数据，不打分、不排名。examples/spot-check →
A fixed set of test requests; data only, no scores, no rankings. examples/spot-check →
回执核验页Receipt checker调试台Playground服务方目录Provider directory持有人操作台Holder console我的服务Dashboard状态Status
参考
Reference
未审计、未部署，主网不可用，仅本地链与测试，今天不收费
not audited, not deployed, not on mainnet; local chains and tests only; nothing charged today