One hop. A record anyone can check.
Metrecept sits on the path between an agent and the model. The caller keeps the key to the lab. What crossed is signed, and a stranger can check that signature without an account.
fingerprint b9b348ce
It enters as the caller sent it. The key stays in their hand.
Each receipt takes a turn. The light is the one just written.
A stranger can check it against the published key. No account required.
Signed
Every record carries an Ed25519 signature. The public key is published, so anyone can check it and read what kind of crossing it was.
Kept
Fingerprints, counts and the price. Your prompt and the answer never leave your side.
Hit or miss
A hit is a repeat request served again, still priced. A miss is the first trip to the lab.
Priced
The session receipt comes with the seat. Other crossings are priced on their own. A page fetch is priced but carries no signature of its own.
Designed to fit your stack
Wrap a generate you already host.
Prompts and completions stay on your box; only digests and token counts cross the pipe.
Two lanes, same meters. The session receipt stays with the seat. The other crossings are priced on the card. You pay the lab separately. The rate card.
Wrap the call
Your machine. Your model.Wrap the model call on your own machine. The install snippet is in Build, for seated members.
The fingerprint and the counts come back. The words stay where they were. A hit means this call has been seen. It is not a saved answer.
The address
https://api.metrecept.co.uk/v1The session
The session, and the crossings inside it.
The model runs where they left it. Metrecept writes down that it ran.
An agent call enters Metrecept. Metrecept sits on the path to the model and signs a session receipt for this hop. Anyone can check that signature against the published keys.
What comes in
The call
- Agents
- Cursor, Claude, and the tools an agent carries. The run can go on after the lab has stopped looking.
- Applications
- Your own code, the libraries, and a generate function that stays on your machine.
- Orchestration
- n8n, webhooks, and the retry that is the same request again.
METRECEPT.
ON RECORDThe session, signed.
The lab's invoice is not the record.
the call · the count · the pipe
What was called, how many times, which door, and what the pipe wrote down. Reading the session does not open a second bill.
Loose of the lab
ON RECORD- [20:31:46] Session receipt · fingerprint d0b35e
- [20:31:46] Hit · fingerprint 2a2e84
- [20:31:47] Read · fingerprint 6f810f
Anyone can check the signature against the published keys. This is not the lab's bill.
Check this oneWhat leaves
- The desk that governs
- It reads the receipt. It does not become the record.
- The review
- What you hold, the rules, and the limits, with the receipt still attached.
- The boundary
- Not a switch that stops the call. A witness on the way to the model.
The invoice
Same crossings. Two cabinets.
The lab's bill
Nothing billed · 0p
The same crossings, on the record
- Hit0.45p · abbd18
- Miss0.1125p · 937dc4
- Fetch2p · cb33e6
- Read0.45p · 444e24
Crossings on the record · 1,287
The fingerprint and the counts. Never the words.
On their metal
The model stays where they put it. What comes across is the fingerprint and the counts. The receipt is of that report.
Past the lab
A hit can finish with nothing owed upstream. The pipe still writes the crossing. A hit is 0.45p per thousand tokens. A miss is 0.1125p.
Through the night
The same record, written while the building is dark, waiting in the morning.
Before a word goes in
Before the model.
01
The address, as given
Nothing is discovered, guessed, or followed past it.
02
The rules, then the screens
If the site refuses, nothing leaves. The address cannot point inward. Personal details are taken out first.
03
A short extract, for this purpose
Tied to why the call was made. Not the whole page.
04
The model
Only that extract reaches it.
▸ The address arrived, as given
A fetch is 2p a page. It has a price. It does not get a signature of its own.
How a fetch is kept inOne organisation, one calendar month
The month.
The month is every crossing one organisation made, from the first hour of a calendar month to the last, counted in UTC. October here is that organisation’s October. Another organisation has its own.
While the month is open, each crossing is written as it happens. A request served again. A request sent to the lab. A page fetched. A call to another service. A note that a record was kept or changed. The prompt is not in the month.
The person who pays the pipe, or who has to say what the agents did, asks for the close. If the month had crossings, that ask writes one signed record of the totals. It costs 7.5p the first time. Asking again does not charge again. You keep the record. It still checks after the live list is gone. You use it when the lab’s invoice arrives and the crossings the pipe answered itself are missing from it.
The close is not taken from that invoice. The invoice number stays empty until a person types the number and the total they were charged, and the total is the same as the sum already written. The lines stay as they were written. If the total does not match, the month stays open.
METRECEPT.
October 2026 · one organisation
- A run, closed · 47 crossings · 30.75p on the pipe
- Served again · 12,400 tokens · 0.45p per thousand
- A record changed · tied to the note before it · 0.75p
612 served again · 401 sent to the lab · 180 pages · 91 calls