核验回执Verify a receipt

1回执Receipt

正在核验本页链接里的回执（#r= 片段）。片段只在你的浏览器里，不会发给任何服务器。Checking the receipt in this page's link (the #r= fragment). The fragment stays in your browser and is never sent to a server.

可以粘贴：核验链接（https://tapeapi.fun/verify/#r=…）、它的 #r= 部分、回执 JSON，或整个 MCP 工具结果（含 _meta["fun.tapeapi/receipt"]，也可以是外层的 JSON-RPC 回应）。最多 64 KiB。Paste the verify link (https://tapeapi.fun/verify/#r=…), its #r= part, the receipt JSON, or a whole MCP tool result (with _meta["fun.tapeapi/receipt"], or the JSON-RPC response around it). Up to 64 KiB.

AI 用量回执也可以：x-tapeapi-receipt 响应头的值（或整行）、流里的 : tapeapi-receipt … 注释行（或整段流），或 receipt 方法的回答。AI usage receipts too: the value (or the whole line) of the x-tapeapi-receipt header, the : tapeapi-receipt … comment line of a stream (or the whole stream), or the answer of the receipt method.

2结论Verdict

这是一份 AI 用量回执。它的两个哈希绑定确切的请求字节与回答（回答的字节；流式回答取其事件数据），本页没有这些字节（除非你在上面粘贴），所以默认只核对签名、服务身份与金额。签名证明的是谁回答的、声称了什么，不证明实际运行的是哪个模型；这类替换靠回执与抽检变得可追责。This is an AI usage receipt. Its two hashes bind the exact request bytes and the answer (its bytes; for a stream, its event data), which this page does not have (unless you paste them above), so by default it checks the signature, the service's identity and the amount only. A signature proves who answered and what was claimed, not which model actually ran; receipts and spot checks make such a substitution attributable.

这份回执带原文：请求参数与结果（或拒绝内容）就在回执里，也就在它的核验链接里，也就是这段对话本身。链接转给谁，谁就看得到问了什么、答了什么；只在愿意分享这些内容的场合分享它。This receipt carries the content: the request params and the result (or refusal) are in the receipt, and so in its verify link; that is the conversation itself. Whoever the link is passed to sees what was asked and answered; share it only where you would share those.

这是只带哈希的回执：它用签名所依据的两个哈希代替请求参数与结果，所以能核对谁在何时签了什么，但本页看不到问了什么、答了什么。哈希只能藏住猜不到的内容：取自小集合的参数（地址、token id、交易对）或简短的结果，别人可以通过对候选取哈希确认出来。This is a hash-only receipt: the two hashes the signature is computed over stand in for the request params and the result, so it shows who signed what and when, but this page does not see what was asked or answered. Hashes hide only what cannot be guessed: params from a small set (an address, a token id, a price pair) or a short result can be confirmed by anyone who hashes the candidates.

回执内容What the receipt says

本页核对什么What this page checks

1. 从签名恢复签名者：签名覆盖容器、请求 id、方法与参数、成功或拒绝、结果、时间。改动其中任何一项，恢复出的就是另一个地址。Recover the signer from the signature, which covers the container, request id, method and params, success or refusal, the result, and the time. Change any of them and a different address comes out.
2. 用回执里的电路合约和 #ID 在链上解析服务（3 家不同运营方的公共 BSC 节点，至少 2 家一致）：容器由中枢推导，清单字节与 SiteRegistry 的哈希一致，委托由当前持有人签署且未过期。Resolve the service on chain from the receipt's circuit contract and #ID (public BSC nodes of 3 different operators, at least 2 agreeing): the hub derives the container, the manifest bytes match the SiteRegistry hash, and the delegation is signed by the current holder and not expired.
3. AI 用量回执不带电路与 #ID：本页按回执里的容器解析服务，再核对金额（按回执里的模型在清单价目表中精确匹配，用回执里的 token 数重算，向上取整到 8 位小数）。An AI usage receipt carries no circuit or #ID: the page resolves the service from the receipt's container, then checks the amount (the receipt's model matched exactly in the manifest's price table, recomputed from the receipt's token counts, rounded up to 8 decimals).
4. 比对：链上推导的容器等于回执里的容器；回执里的名字属于这个服务；恢复出的签名者等于清单今天指定的签名密钥。Compare: the container the chain derives equals the receipt's; the receipt's name belongs to this service; the recovered signer equals the signing key the manifest names today.

回执不证明什么What a receipt does not prove

• 回执不证明实际跑的是哪个模型或哪段程序：它证明谁的密钥、对哪个请求与回答、在什么时间签了名，以及服务声称的用量与价格。AI 回执里的 model 是上游报告的名字。A receipt does not prove which model or which program actually ran. It proves whose key signed which request and answer, and when, and the usage and price the service claimed. The model in an AI receipt is the name the upstream reported.
• 带原文的链接（MCP 回执 v 1）里含对话内容：请求参数与结果都在链接里，拿到链接的人都看得到。默认的链接只带哈希，但取自小集合的参数（地址、token id、交易对）或简短的结果仍可能从哈希猜出。A link with content (an MCP receipt v 1) contains the conversation: the request params and the result are in the link, for anyone who gets it. Default links carry hashes only, but params from a small set (an address, a token id, a price pair) or a short result can still be guessed from their hash.
• 元数据不隐藏：服务方看得到你的请求与 IP；本页读链时，公共 BSC 节点看得到你的 IP 和你在查哪个服务。Metadata is not hidden: the service sees your request and IP address; while this page reads the chain, the public BSC nodes see your IP address and which service you are checking.

手上没有回执？在调试台里调用一个方法，或者用 MCP 端点 https://api.tapeapi.fun/mcp：每个工具结果都带核验链接。No receipt at hand? Call a method in the Playground, or use the MCP endpoint https://api.tapeapi.fun/mcp: every tool result carries a verify link.