Questions, answered.
How recordation works, where the gap is, and what stays private.
What is recordation?
Recordation commits a usage record before the invoice goes out. Both the provider and the customer can open the same record, and it reads the same for both. The provider still produces the numbers. Recordation gives both sides one shared copy to work from.
Is PacSpace a billing system?
No. PacSpace sits alongside billing. The provider keeps metering and invoicing exactly as they do today. PacSpace commits the record both sides reference, so the invoice has a shared source instead of a one-sided one.
What does PacSpace actually do?
It records. It commits the usage to a record before the invoice, keeps that record consistent for both sides, and lets each side check it directly. It does not decide who is right.
Where is the gap in usage-based billing today?
One party measures the usage, produces the invoice, and holds the only record of what happened. The customer reads that number through the provider's dashboard or export. There is no second, independent copy to check it against. So verifying the bill usually means asking the provider to confirm the provider's own number.
What does verification actually require?
Three things: evidence the checker did not produce, cannot change, and can reach without asking permission. A dashboard the provider owns and controls meets none of the three, however well it is built. That is the gap, and it is structural, not a question of anyone acting in bad faith.
Isn't a clear, real-time dashboard enough?
A visible meter is a real improvement to the experience. It shows the number plainly and in the moment. But visible is not the same as verified. The number is still produced and held by one side. Recordation adds the part a dashboard cannot: a shared record both sides can check.
What stays private when we use PacSpace?
Your data does. The contents of every record, what was consumed and how much, are never published and no third party ever sees them. Either side can still check that a record is intact, but that check carries none of the underlying detail. Checkable by both sides, seen by no one else.
Is our data exposed? Who can see the record?
The record stays private, between the vendor and the customer. Nothing is published. No third party sees the contents.
If the record is private, how does the customer verify it?
The customer is the verifier. They check the same committed record directly. Verification comes from the shared record itself, not from making anything public.
Is anything published where others can see it?
No. Nothing about your data is published, and no third party sees what a record contains.
Does PacSpace decide who is right in a dispute?
No. PacSpace records, it does not decide. The record shows what was committed. Transparency, not correctness. It is a notary, not a judge.
If the provider pays PacSpace, how can it be neutral?
Neutrality is structural, not a matter of who pays. The record is produced the same way regardless of who is asking, reads the same for both sides, and PacSpace's revenue is decoupled from any outcome. A notary paid by the signer is still a notary.
Is PacSpace an auditor?
No. We never audit, arbitrate, score, rank, or meter. We commit the record, and both sides read it.
How often does PacSpace record?
You control the cadence. Each record is a delta, one committed change in a customer's usage, and you choose how often to commit one. The default is a daily flush, which lines up with how invoices close. When you want closer to real time, commit deltas more often, down to hourly or smaller, and set the resolution per customer. Verification works the same at every cadence, so finer granularity is a feature you can offer, not a limitation.
Once a record is committed, can it change?
No. Once committed, the record reads the same for both sides, every time. It is the one fixed reference you both return to, so a number cannot quietly drift between when it was recorded and when it is questioned.
What does the provider get out of it?
Engineering time back and deals that move. Your team stops reconciling token counts against customer telemetry and ships product instead. Finance closes the books on schedule. Procurement reviews that used to stall on unverifiable usage clear, so larger contracts close faster. And every renewal opens from a record both sides already trust, instead of relitigating last quarter's invoices. One record turns billing from a recurring argument into a non-event.
What does the customer get?
Confidence in the bill, without the back-and-forth. They check it against the same record the provider used, on their own and in minutes, with no support ticket and no waiting on a reply. It is spend they can stand behind in their own reporting, and one less line item they have to take on faith. The invoice stops being something to brace for and becomes something they can simply confirm.
How do we adopt it?
Talk to us. We will walk through where recordation fits in your stack.
Why start with inference billing?
Inference is the sharpest case. Tokens and compute are measured entirely inside the provider, so the customer has no way to run a parallel meter. It is where a shared record helps most. The same architecture extends to any usage-based exchange, and eventually to machine-to-machine commerce.