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

Four API calls. That's it.

Record, derive, compare, checkpoint. Each step builds provability into your billing — so when numbers disagree, the math resolves it.

From usage event to
verifiable proof.

01

Emit — Record usage as it happens

Every time usage occurs, you record it as a signed delta through the Balance API. PacSpace generates a fingerprint and permanently records it. Your counterparty gets a receiptId they can use to verify the event independently. Once recorded, the delta cannot be altered or deleted.

POST /api/v1/balance/delta
// Request
{ customerId, delta, reason, referenceId }

// Response
{ receiptId, status: "QUEUED", fingerprint }
02

Derive — Compute the verifiable balance

PacSpace maintains an ordered log of all verified deltas. Request the current balance for any customer at any time — it's computed on demand from the immutable record. Both parties can derive the same balance from the same data. Same inputs, same math, same result.

GET /api/v1/balance/derive/:customerId
// Response
{ balance, deltaCount, lastVerifiedIndex }
03

Compare — Surface discrepancies instantly

When numbers don't match, both parties compare against the neutral record. The API returns the exact point of divergence — which deltas are disputed, which are confirmed. Discrepancies become math problems with precise answers, not open-ended investigations.

POST /api/v1/balance/compare
// Request
{ yourBalance, counterpartyBalance }

// Response
{ match: false, discrepancies: [...] }
04

Checkpoint — Lock period-end proof

At period-end, commit a tamper-evident proof root over all verified deltas for the billing window. Include the checkpoint fingerprint in your invoice so your counterparty can independently audit the entire period with a single verification call.

POST /api/v1/balance/checkpoint
// Request
{ fromIndex: 0, toIndex: 1499 }

// Response
{ proofToken, proofHash, deltaCount: 1500 }

What is a verified delta?

A verified delta is a permanent record of a balance change. PacSpace generates a mathematical fingerprint — like a notary who stamps the envelope without reading the letter — and commits only that fingerprint to the permanent ledger.

You share the verification proof with your counterparty. They can independently prove it matches the permanent fingerprint. The proof resolves it — not a phone call.

See integration examples

Immutable

Once recorded, a delta cannot be altered or deleted by any party. The fingerprint is permanent.

Neutral

PacSpace has no stake in the outcome. We don't control your records or decide who's right. We verify the math.

Private

Only fingerprints are stored permanently. Your data never leaves your systems.

Provable

Any party can independently prove a delta exists and hasn't been modified — without accessing the underlying data.

Per-customer isolation

Every customer ID automatically gets its own isolated ledger. No setup needed.

Learn how to verify a proof →

What's on the ledger

Your data — Private
Customer ID cust_8xKj2m
Amount -182 GPU-hrs
Reason gpu_burst_capacity
Reference job_abc123
Metadata { region, plan }
Permanent ledger — All that's stored
Fingerprint 0x8f3a9b2c...
Index 1042
Verified true

Five fields of your data. Three fields on the ledger. Zero overlap.

Every customer gets their own ledger

Pass a customer identifier with each delta. PacSpace derives a unique, isolated ledger for that customer automatically. No setup required.

Each customer's deltas, balances, and checkpoints are independently verifiable. One customer's data never intersects with another's.

Learn more →

Isolated

Each customer ID maps to its own independent ledger. No cross-contamination.

Private

PacSpace stores only derived identifiers, never real customer data. You control the mapping.

Automatic

No configuration needed. Pass a customer ID with your first delta and the ledger is created instantly.

Ready to make your billing provable?

Integrate in minutes. Start verifying today.

Request access See integration examples