Counter-Receipt
GPReceipt’s counter-signed tier: one record, signed by both sides.
When two systems work together — an agent and the service it calls, a client and the server that lets it in — each keeps its own log, and each log can only vouch for its own side. Counter-Receipt closes that gap. The other party issues a small signed statement of what it checked and what it allowed: a counter-receipt, free to produce with our open kit. We verify it, match it to our receipt of the same moment on a key that carries no personal data, keep the matched pair on a tamper-evident ledger, host the partner’s published keys, and alert you when a record is missing or the two sides disagree.
Anyone can check any record without Trothward. What we sell is the matching, the keeping and the watching.
Who it is for
- Interoperability programs. Participants who today file logs by hand after every test, and the organisers who grade them. A matched pair is the evidence they look for, produced as the test runs.
- Services that let many clients in. Authorization servers, identity providers and MCP server operators who want proof of what they allowed, signed by the other side.
- Institutions and professionals. Anyone who needs a dispute-proof record of an agent’s action, with the counterparty’s signature beside our own.
What you get
Five levels. Whoever keeps the record pays; checking or signing is free.
| Level | What it includes | Price |
|---|---|---|
| Open | The kit: verify a receipt, verify a counter-receipt, generate a counter-receipt. The Standard text. | Free. Kit Apache-2.0, text CC BY 4.0 |
| Recorded | A sealed receipt of each act. | Metered per unit |
| Joined | We take in your partner’s counter-receipt, verify it with the kit’s own code, and match it to our receipt check by check (agreed, disagreed, missing). The matched pair is sealed on the ledger, with links anyone can check. | From 0.6¢ per matched pair |
| Watched | Hosted key document for each counterparty (rotation, retirement, compromise). Expected-vs-received per counterparty, alerts by Governed Email, and a conformance grade over time. Includes the hosted generator for partners who will not run the command line. | From $25 per counterparty per month, 5,000 pairs included |
| Program | All of the above across every participant of a conformance program: the matrix as a live view, exported in the organiser’s own template. | Quoted |
Try it
- Get the kit. Standard library Python, no account, no network unless you ask. It runs on your machine with your key, and never sends it anywhere.
- Make a counter-receipt from your own logs.
(Shortened; see the kit’s help.) Your raw values are hashed, never written.
python3 counter_receipt.py generate --profile ema_redeem --log your-log.txt --line 42 --checks checks.json --outcome allowed --key your-key.pem --key-ref https://you.example/keys.json --out counter-receipt.json - Check one of ours, now. This is the approval record of a real three-party test from
18 October 2026. Select it: it re-checks in your browser, no account, no key.
The receipt of the executed call is checkable the same way: verify.braas.dev/act/sha256:473dd7ba…/verify
00mve8t9dm-cdb9581971a5db12
What is live, and what is coming
- Live: the Standard (counter-receipt profile, §Receipts-A1); keyless checking of every record at verify.braas.dev; our own counter-receipts from live interoperability tests.
- Coming: the open kit’s public release; the Recorded, Joined, Watched and Program levels, which are in build now.
- Not yet: a counter-receipt issued by a partner. The first one is what we are working toward.
The mechanism is live. The product is in build. We will not call it more than that until it is.
Read the Standard: Governed Agent Authority Standard · Trothward products: Governed Email · GPReceipt · GPAgent · Counter-Receipt