FREE DEMO · NO WALLET · NO ACCOUNT
Verify the response.
See what changes.
An agent receives a response and hands it to another agent. A signed receipt lets the recipient check whether those bytes match the retained declaration.
Try the browser demonstration →
The verifier offers an intact example and an altered response. The first passes; the second keeps a valid receipt signature but fails the content check. Verification runs locally.
Try it from your agent
Read the MCP resource datoka-api://demo-receipt, then pass its JSON to verify_api_receipt. This receipt already exists: no purchase is needed.
Read datoka-api://integration for the complete capture, preparation, purchase and recovery guide. MCP endpoint: /mcp (Streamable HTTP).
Inspect the files
- Receipt JSON for the free verification tool
- Evidence bundle including the synthetic response
- Public keys for this demonstration
- Offline verification script · SHA-256 manifest
For your own receipts, establish trust in the issuer independently. Keys supplied alongside a demo show how verification works; they do not independently establish identity.
When to buy
Buy when a recipient needs a third-party signed commitment for an API response handoff, retained decision input or archive integrity. A local log may suffice for disposable data.
0.002 USDC per receipt on Base. Preparation and verification are free. Purchases require an approved budget. Use the recoverable purchase example.