How it works

The Shared Record, piece by piece.

Your billing stays where it is. PacSpace adds one artifact: the Shared Record.

Shared Record
June 2026 · 2026-06-01 to 2026-06-30 · UTC cycle
Sample
Usage recorded this cycle
3,847,759,431
Inference tokens
Daily usageHover a day to trace it · tap a day to open it
S
M
T
W
T
F
S
recorded today (UTC) upcoming
Checkpoint · locked through Jun 16 Cycle receipt · available after Jun 30
Recorded by the vendor · Verified through PacSpace
The artifact

One record. Both sides. This is it.

Today, the meter behind every usage bill is a black box: only the seller can see inside, and the buyer is billed whatever the meter says. PacSpace makes the meter's record shared, fixed, and private. Both sides hold it, neither can change it, no one else sees it, and it exists before the bill does. That is the Shared Record.

01 · The cycle

The number the invoice carries

One number per cycle, built from committed windows. A checkpoint locks everything behind it as it goes.

Show the cycle view
02 · The day

Questions start from one entry

Any day opens to its entries. A question starts from one committed entry, not a disputed total.

Open June 9
03 · The proof

Checkable by either side

Every entry carries a proof either side can check, independently. No account, no permission to ask for.

Verify an entry
Versus the dashboard

The dashboard shows usage.
The record makes it checkable.

A perfect dashboard is still your word. Your customer can read it, never check it. Checking needs a copy both sides hold. The record is that copy.

The usage dashboard
The Shared Record
Where it lives
Inside the vendor's account, behind a login.
With both sides. The invoice link opens it, no account, no signup.
What it shows
The live read of the vendor's systems.
What those same systems reported, committed before the invoice went out.
When you look twice
Live numbers move. Yesterday can read differently today.
The record keeps growing. What was committed yesterday reads the same today, for both sides.
When a correction lands
The number updates in place. The earlier read is gone.
Corrections are new entries with stated reasons. The original stays visible.
When a bill is questioned
The answer comes from the same system that produced the bill.
The answer is a committed entry both sides already hold.
What you can cite
A screenshot of a page.
A proof reference either side can check, independently.

Keep the dashboard. Add the record. One shows usage as it happens. One settles what the bill points to.

The flow

Three steps. One of them is yours.

You wire it in once, alongside the billing you already run. After that, every cycle runs on its own, and each step leaves a guarantee behind.

The step
The guarantee
01
You
Commit the window

Your billing job commits each customer's usage, on the cadence you set.

The guarantee
Committed before the invoice.

The record exists before the question does. The timestamp is part of it.

02
PacSpace
The record is fixed

Once committed, it reads the same every time it is opened, for both sides.

The guarantee
Revisable by no one.

Including us. Corrections are visible entries with stated reasons, never quiet edits.

03
Either side
Open the record and check

Your customer opens it from the invoice link. Checking needs no one's permission.

The guarantee
Durable beyond us.

Checking does not require PacSpace to exist. The verification survives the company.

One integration, wired once.