Metrecept
The Suite is the desk. Eight faces on the hop: input, bias, gain, delay, filter, output, clock, and checker.
It sits on the request hop. The receipt is fixed to the clock hour. The row is the FOCUS grain of what ran, not an estimate pasted into the bill.
01 / Two surfaces
The desk and the suite are the two faces of the same hop. Each one carries the other.
Surface
An eight-device horizontal signal chain and real-time Merkle clock. Watch every request cross input, bias, gain, delay, filter, output, clock, and checker in real time.
Platform & AI Engineers
Tuning routing spreads, prompt cache replay states, and token payloads.
Surface
Receipts, Export, the model router, the custody slip, and Enterprise. The row is what finance reads.
FinOps Leads & CFOs
Reading the row, the export, and the custody slip.
FinOps
One leaf, standing on its own.
When the lab portal goes dark, the live API chokes, or the issuing protocol goes offline, a standard log is trapped behind a dead door. A Metrecept receipt doesn't wait for the door to open. Its proof lives entirely in two uncompromising facts: the cryptographic signature and the Merkle inclusion.
The day an accounting period closes is notoriously the day a vendor's dashboard refuses to load. It doesn't matter. The charged figure for the compute hop—along with the exact model, the execution plane, and the region—is already burned into the receipt in your hand. The fixed clock hour is where the leaf permanently sits. Verifying those figures doesn't require waking up the portal, nor does it require inspecting the leaves sitting beside yours.
The portal is a courtesy for the days when the lights are on. The receipt is the hard truth you hold when they go out.
To prove a mint happened, a holder needs only the receipt, the leaf, the Merkle path, and the root of that fixed clock hour. The signature verifies against the published directory; the leaf's inclusion verifies publicly via /v1/public/clock/inclusion. Even if the entire lab infrastructure vanishes, those two mathematical realities remain intact. A billing period may be a continuous run of leaves, but this single leaf does not borrow its legitimacy from the crowd.
You verify the leaf in total isolation. You never query the minting engine, and you never audit the surrounding tree. The single crossing in your hand is the entirety of the inquiry. The rest of the month's data can wait—the figure on your receipt answers only to itself.
Banking
The file is the final word.
Once a mint is struck, a verifier is never sent cap-in-hand back to the operator to ask whether the compute hop "still counts."
Banking has spent centuries navigating the gulf between a bearer instrument and a letter of intent that arrives after the fact. The Metrecept receipt is forged in that exact distinction. The signing pipe seals the receipt at the exact moment of the mint and locks the leaf into the clock hour. Whatever the operator chooses to write tomorrow is merely commentary. It cannot stand where the signature stands, and no retroactive ledger edit can uproot the leaf.
The moment the hop occurs, the pipe signs the receipt and plants the leaf inside the clock hour. The inclusion path is the immutable route from that single leaf to the hour's root. Whoever holds the file verifies the file directly. The operator is stripped of the power to be called back in and declare that, upon further reflection, the transaction no longer stands.
If an operator issues a conflicting statement later, it is just a separate piece of paper. The signature on the original receipt still resolves against the directory, and the inclusion check still anchors the leaf to its birth hour. You can put both documents on the table, but only one of them was cryptographically present at the mint.
Insurers
The hour is a physical place, not a claim.
The inclusion check is binary: either this leaf sits beneath the published root of that specific clock hour, or it does not.
Insurers spend their lives auditing "when"—usually handed a timestamp by a party with a strong financial incentive to prefer one when over another. In traditional logs, a timestamp is just a polite assertion. In a fixed Merkle clock, the hour is not a figure of speech; it is structural geometry. The root of that clock hour is published to the world. The leaf is mathematically trapped beneath it, or it isn't there at all. A more convenient timeline, invented after the loss, is just fiction. It has no cryptographic path into the tree.
The bond between the mint, the leaf, and the clock hour is mathematically fused. Chronology is no longer a coordinator's mutable timestamp; it is architecture. A second mint creates a second leaf. Attempting to rewrite the receipt shatters the signature, and attempting to backdate an event fails the inclusion check against the published hour root. Two events that desperately want to share an alibi cannot share a leaf. Each is permanently bolted to the hour that birthed it.
04 / The lifecycle
The desk writes the row for the hop. An estimate stays out of the billed column.
The Hop takes many diverse forms.
Written at gain, and only if bias let the hop through. ListCost is the published price. ContractedCost is the lane price. BilledCost is what the pipe charges. EffectiveCost is what remains after a credit is drawn down. If bias refuses, the provider is not called and these columns are not written.Gain
A figure for what the lab price might have been, kept in its own column and marked estimate-only. It is never added into BilledCost.Gain
A named prepaid credit is one Purchase row, written at bias. At gain the usage row bills zero, and the pipe charge is kept on the row as a tag so the unit cost can still be read.Bias, then gain
Readings that are not prices: tokens in, tokens out, the tier that was asked, the mechanism that ran, heel, and fig. A provider key is never written here.Input, gain, filter
What enters. The request is taken as it was sent. How much came in is noted, and a fingerprint is kept of those exact bytes, so a later request can be compared with this one. The words themselves are not kept on the record.
The condition already in place, checked before anything is sent on. The limit, and any money already paid in, are looked at first. If the limit is used up, or nothing remains, the request stops and no call is made. Money paid in advance is recorded here as a purchase.
Where the amount is set, if the request was allowed through. The price that was asked and the price of what actually ran are kept apart, so a cheaper path is not blended into one number. The published price, the agreed price, the amount billed, and the amount left after any credit are written together.
A comparison with something already held. The note says whether this request is the same, different, not known, or not there. That note does not, by itself, make the charge a free repeat. When the same bytes are served again, the repeat is still charged as use, at the repeat price.
A filter keeps some things out of the price. If the text taken in was charged, notes about that wording are written beside the row. They describe the language. They are not added to the bill, and they do not decide whether the request goes through.
What came out. A fingerprint is taken of the response, so someone can check that these exact bytes left, rather than a description of them.
A clock marks when. The signature says which key signed the record. The clock says which hour that was, and that hour is not changed later.
A check of the finished record. It reports what it finds, such as a limit already crossed, or this month moving away from the last one that was closed. The report does not add a charge, and it does not change the amounts already written.
The close. The month is not closed by fetching a vendor bill. The invoice number stays blank until a person types a total and that total matches the sum already billed. Only then is the file closed.
The row carries InvoiceId, SkuId, ConsumedQuantity, PricingQuantity, ListCost, ContractedCost, BilledCost, EffectiveCost, x_EstimatedProviderAvoidedUsd, x_EstimateOnly, and Tags.
A finance lead can take three usage logs, each with its own header, and read them as one ledger. The model name is the SKU. Tokens and images use the quantity columns the rest of the books already have. The cost is the amount on that log.
| BillingAccountName | ServiceProviderName | HostProviderName | SkuId | ConsumedQuantity | ConsumedUnit | PricingQuantity | PricingUnit | BilledCost |
|---|---|---|---|---|---|---|---|---|
| Example Bank | Standalone Lab | Standalone Lab | gpt-4-turbo-2024-04-09 | 2000000 | Tokens | 2000 | 1k Tokens | 40.000000 |
| Example Bank | Cloud Lab | Example Cloud | frontier-chat | 250000 | Tokens | 250 | 1k Tokens | 8.000000 |
| Example Bank | Cloud Lab | Example Cloud | image-gen | 400 | Images | 400 | Image | 12.000000 |
This is what the company pays for the crossing, not what it pays the lab. A cache hit is still usage, at the hit price. The estimate of lab spend that may have been avoided is shown beside the bill. It is not added to it.
| Hit | Miss | |
|---|---|---|
| ChargeCategory | Usage | Usage |
| ConsumedQuantity | 2000 | 1000 |
| ConsumedUnit | Tokens | Tokens |
| PricingQuantity | 2 | 1 |
| PricingUnit | 1k Tokens | 1k Tokens |
| BilledCost | 0.012000 | 0.001500 |
| SkuId | metrecept.v4.cache_hit | metrecept.v4.cache_miss |
| ServiceCategory | AI and Machine Learning | AI and Machine Learning |
| ServiceProviderName | Metrecept | Metrecept |
| Model, in Tags | mock | mock |
| Estimate of provider spend avoided | 1.500000 | 0.000000 |
| Estimate only | true | true |
A training job that ran on machines this record never saw is not written down as if it had. There is no guessed row to fill the gap. If the work did not come through, it is not on the bill.
A closed month is what was spent. A picture of the month ahead is what someone expects. The picture can be shown beside the books. It is not allowed to sit in the column that says what the money was.
The lab invoice is not pulled in the background and treated as already true. The month stays open, and the invoice number stays empty, until a person types the total they are holding and that total matches the sum already written here.
A request can be aimed at a costly model and answered by a cheaper one. Both facts are kept. They are not stirred into one rate that hides the choice. A reader can see what was asked for, and what actually answered.
The columns are the ones a finance reader already knows. A note that is not a price is written beside the row, under its own name. A new idea does not become a new column.
We use storage that is strictly necessary to sign you in and run checkout. With your consent we also count anonymous page visits. Privacy