Before your agent acts, AgentOracle checks the claim and issues a signed receipt — evidence anyone can verify offline, against published keys, without trusting us or you.
One API call sits between your agent and its consequential actions. Here is the whole product:
"This invoice is unpaid." "This drug interaction is safe." "This customer is eligible." The claim that justifies the action.
Independent sources, adversarial re-checks, a published rule table — before the action runs, not after it goes wrong.
Canonical bytes (RFC 8785), Ed25519 signature, the verdict, the sources, and the exact rules used — sealed at issue.
Offline, against published keys. Auditors, counterparties, courts — no account needed, no trust in us required.
Don't take the homepage's word for anything. Pull a real receipt off this site and verify it on your own machine, offline.
The verifier is MIT-licensed, under 250 lines, no dependencies on us. Read it before you trust it — that's the point.
agentoracle-mcp is a Model Context Protocol server for Cursor, Claude Desktop, Codex, and any MCP-compatible client. Verify signed receipts, check confidence scores, and pull the current JWKS — from inside your editor.
Point at a receipt file or URL, get valid: True — or the exact reason it isn't — without leaving the editor.
The MCP server runs locally, verifies against the public JWKS, and never phones home.
Receipts the MCP verifier checks are byte-identical to the ones the reference verifiers produce.
Published on npm as agentoracle-mcp.
A log is the operator's story. A receipt carries its own evidence — verdict, sources, rules, signature.
Letting the operator keep the record is letting the suspect write the police report.
Change one byte and the signature fails. Backdating fails the same way — timestamps are bound in.
Published keys, canonical bytes. If we disappeared tomorrow, every receipt still verifies.
An independent team rebuilt the format from the spec text alone — matching to the last byte.
IETF-filed, MIT reference code, published conformance vectors in two languages.
The EU AI Act's record-keeping obligations (Article 12) bite December 2027. Receipts are records an external examiner can verify without trusting you — built for exactly that clause.
Give every consequential agent action an evidence trail. One API call in the loop; a receipt in every audit bundle, ready for whatever governance stack sits above you.
Finance, health, legal — anywhere "the AI said so" isn't a defense. When something is questioned, hand over proof instead of promises.
Checkout with a card, get an API key instantly. 2,000 verifications a month, full signed receipts, the works.
For autonomous agents paying their own way: x402 pay-per-call with USDC, gasless via SKALE. No subscription, no account — the agent pays, the receipt returns.
Volume, SLAs, custom mapping tables, composed multi-issuer receipts, co-signing with your own keys.
No — card checkout gets you an API key. Wallets are optional, and only for the x402 pay-per-call path used by autonomous agents.
That a specific claim was checked at a specific time, against named sources, under a published rule table, producing a specific verdict — and that none of it has been altered since. It proves what was checked and what the answer was. It doesn't prove things it can't: our whitepaper publishes the limits next to the strengths.
Install the MIT-licensed verifier (or write your own from the IETF draft — a team already has, byte-identically). Verification runs offline against our published public keys. You never need our permission, our API, or our continued existence.
Article 12 requires records of high-risk AI operation, applicable December 2027. Receipts are records that verify independently — the property plain logs can't offer an examiner. We publish a free Article 12 mapping in the whitepaper.
You get the same signed receipt with verdict "do_not_act" and the contradicting sources sealed in. The "no" is evidence too — often the more valuable kind.
Yes — that's the x402 path: the agent pays per verification in USDC (gasless via SKALE) and gets the receipt in the response. Built for agent-to-agent commerce.