Balance API Overview Who's This For How It Works Verification Integration
Neutrality Company Thoughts Docs
Private Beta

Four API calls to
verified settlement.

Record usage deltas. Derive verifiable balances. Compare both sides. Checkpoint at period-end. The Balance API turns billing disputes into math problems.

Request access Read the docs
Your System Record usage
PacSpace Fingerprint & Verify
Your Customer Prove on invoice
The Flow

Four calls. Verified settlement.

01
Emit

Record usage as a signed, immutable delta.

02
Derive

Compute the verifiable balance on demand.

03
Compare

Surface the exact point of divergence.

04
Checkpoint

Lock period-end proof for invoicing.

See the full technical walkthrough →
The result

One proof for an entire period.

Each billing window produces a single checkpoint — a tamper-evident fingerprint covering every verified delta in the period. Attach it to an invoice, embed it in a dashboard, or expose it through your API. Your counterparty can independently confirm the entire period without involving you or PacSpace.

Verification Paths

Works with one party.
Even better with two.

One side integrates PacSpace. The other side never has to. Both get the same verifiable record.

Most common

Accept the receipt

"I trust the invoice."
Your counterparty sees the checkpoint on their invoice and pays. No friction. PacSpace is invisible to them.
Disagreement

Resolve with proof

"Our numbers don't match."
Both sides compare against the verified record already on the ledger. The math either confirms or clarifies the difference — no emails, no escalation.
Best case

Both sides adopt PacSpace

"We want shared truth."
Your counterparty integrates PacSpace on their side. Disputes become impossible — both systems record through the same neutral infrastructure.
See how verification works →

Stop debating the numbers.

Start proving them.

Request access Read the docs