Recordation infrastructure for metered commerce

We make the usage bill checkable.

The customer behind the meter is becoming a machine. Tokens, GPU-hours, API calls: every metered bill is built from a number only the seller can see. The buyer can read it, never check it, so spend runs on faith, and faith caps how far spend scales. PacSpace replaces faith with a record both sides hold, committed before the invoice. This is that 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 test

What checking requires.

Three conditions, and a claim has to meet all of them. Miss any one and there is nothing to check, only something to believe.

The condition
Metered usage today
01

Evidence the checker didn't produce.

Metered usage today

Produced by the seller.

02

Evidence that doesn't move.

Metered usage today

Moves with the seller's systems.

03

Evidence either side can reach without asking.

Metered usage today

Reachable only through the seller.

The Shared Record passes all three.

The Shared Record

One record of the usage. Both sides hold it.

Shared.

Both sides open the same copy, without asking anyone's permission. The invoice link opens it: no account, no signup, nothing to install.

Fixed.

It reads the same every time it is opened, for both sides. Corrections are new entries with their own stated reasons, never edits.

Private.

Never published. The contents are shown beyond the two parties only by the record holder's deliberate, revocable choice.

How it fits

Grow usage-based revenue
without growing dispute overhead.

It adds a record and replaces nothing. Three steps, wired once, and both sides come out ahead.

The step
What it means for you
01
You
Usage is committed

Your billing job commits each customer's usage to the record, on the cadence you set. One integration, wired once.

If you send the invoice

Nothing to rip out. Metering, rating, and invoicing stay exactly where they are.

If you pay the invoice

The record exists before the bill does. The evidence never depends on asking for it.

02
Either side
The invoice carries its link

Every invoice carries a link to its record. Your customer opens it with no account, no signup, nothing to install.

If you send the invoice

Procurement clears, and every renewal opens from a record both sides already trust.

If you pay the invoice

Open the record from the invoice and check the bill in minutes, on your own.

03
Both sides
Questions become lookups

Both sides open the same record, and the conversation starts from one committed entry instead of a disputed total.

If you send the invoice

Billing questions stop reaching engineering. The proof existed before the question was asked.

If you pay the invoice

Agent and AI spend that survives review.

Buyers spend more because sellers can be checked.
Sellers earn more because buyers can check.

Agentic commerce

Software is now the buyer.

One agent, buying API calls at auction
The agent's Shared Record · API calls recorded

No human reads at this speed, and no one can reconstruct it after. Delegation scales exactly as far as the record does.

The same record, read by a different buyer at a different speed.

See what changes when software buys →

Questions, answered.

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.

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.

Does this work when agents transact with agents?

That is where it matters most. When software is the buyer, nobody is reading the bill, and manual reconciliation is impossible at machine speed. Agent-to-agent activity is recorded as it happens, checkable by both counterparties and their auditors. PacSpace never moves the money; it records what happened between the two agents, so neither side has to trust the other's log.

What stays private when we use PacSpace?

Your data does. The contents of every record, what was consumed and how much, are never published. Either side can still check that a record is intact, but that check carries none of the underlying detail. Showing the contents to anyone beyond the two parties is the record holder's deliberate, revocable choice. Shared. Fixed. Private.

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. Payment can corrupt discretion. It cannot corrupt a record that has no discretion in it.

How much engineering work is the integration?

One integration, wired once. When your metering closes a window, your system commits that customer's usage as a delta. It is designed to land as a small addition to an existing billing job, with no migration, no parallel billing system, and nothing to rip out. The docs walk through it end to end.

What does it cost?

A monthly subscription with an included volume of verified deltas, and overage at your plan's per-delta rate. No percentage of your revenue, ever: pricing is per verified delta recorded, never per dollar moved. Talk to us for current plans.

See every question →

The record is one integration away.