Balance API Company Thoughts Docs
Private Beta

Balance API

Record credit deltas as usage happens. Create immutable receipts that both parties can verify. When numbers drift, the neutral record brings them back together.

Request access
Their system
Your system

Numbers drift.
It's structural.

In usage-based models, you and your customer track the same activity independently. Even when both systems are correct, they measure different things—and the numbers diverge.

The problem isn't bad systems. It's the absence of a shared truth at the boundary.

Different timestamps

Your system records when processed. Theirs records when sent. Both are "right."

Different definitions

What counts as a "call"? Retries? Failures? Definitions drift over time.

No neutral record

No third party captured the event. No way to resolve without one side conceding.

Three API calls. That's it.

1

Emit

/balance/delta

Record credit deltas at transaction time. Each event is signed, timestamped, and assigned a unique receipt ID. You can't change it afterward—that's what makes it neutral.

2

Query

/balance/derive

Any party can independently derive the current balance by replaying verified deltas. You, your customer, or an auditor—everyone arrives at the same number.

3

Verify

/balance/compare

When numbers diverge, both sides compare against the neutral record. Small variances settle automatically. Large variances resolve on evidence, not arguments.

What is a verified delta?

A verified delta is an immutable, neutral, atomic record of a balance change. When you record a credit delta through the Balance API, PacSpace commits it to tamper-proof infrastructure with a cryptographic fingerprint that any party can independently verify.

Your data stays private—only a cryptographic fingerprint is stored in the permanent record. Your counterparty can verify a delta by comparing the metadata you share against the neutral record. No intermediary required.

Immutable

Once recorded, a delta cannot be altered or deleted by any party.

Neutral

Neither party controls the record. The neutral record is the source of truth.

Private

Only cryptographic fingerprints are stored externally. Your data stays in your database.

Verifiable

Any party can independently prove a delta exists and is unmodified.

Anatomy of a verified delta
// Your API call
POST /v1/balance/delta
{
  "customerId": "cust_12345",
  "delta": -1000,
  "reason": "Monthly usage charge"
}

// What you get back
{
  "receiptId": "rcpt_a1b2c3...",
  "status": "verified",
  "fingerprint": "a1b2c3d4e5f6..."
}

// Period-end checkpoint
{
  "fromIndex": 0,
  "toIndex": 1499,
  "proofToken": "ef01ab..."
}
// ^ attach to invoices for instant verification

Sub-cent economics.
Real ROI.

We batch events into immutable receipts at sub-cent per verified delta. Your data stays private, but the proof is permanent—and independently verifiable by any party.

Stop pulling engineers into billing disputes. Stop giving away credits to end arguments. Stop losing deals because finance can't verify the numbers.

<$0.01 per verified delta
30% of engineering time saved from billing reconciliation
3-5 days per month saved for finance teams
20-50x potential ROI on dispute reduction

Simple to integrate

Record deltas as usage happens. We handle the rest—batching, recording, and verification. Your billing system stays the same.

// Record a credit delta
const response = await pacspace.balance.delta({
  customerId: "cust_12345",
  delta: -1000,
  reason: "api_usage",
  referenceId: "req_abc123"
});

// Store the receiptId for later verification
const { receiptId } = response;

// Later: derive the balance from verified deltas
const balance = await pacspace.balance.derive("cust_12345");

Webhook delivery

When a delta is permanently verified, we deliver a webhook to your endpoint with the complete receipt. HMAC-signed for security.

delta.verified POST
{
  "type": "delta.verified",
  "receiptId": "rcpt_cmh1abc123...",
  "fingerprint": "a1b2c3d4e5f6...",
  "verification": {
    "verified": true,
    "discrepancies": []
  },
  "verifiedAt": "2026-02-10T14:32:01Z",
  "status": "success"
}

Signed & Verified

Every webhook includes an HMAC-SHA256 signature in the Pacspace-Signature header. Verify the payload before processing.

Pacspace-Signature t=1730295134,v1=abc123...
Pacspace-Event delta.verified
Idempotency-Key rcpt_abc123:tenant_...

Manage everything in one place

API keys, webhooks, usage monitoring—all from a clean, intuitive dashboard.

PacSpace Dashboard - API Keys, Webhooks, Usage

End the argument.

Join usage-based platforms building on neutral ground.

Request access Back to home