Introduction
PacSpace records usage before the invoice. Both sides can check the same record later.
What this is for
You charge customers based on metered usage. Before the invoice goes out, PacSpace records the usage and creates a proof.
Written by one side. Visible to both. Owned by neither.
Four calls integrate into your existing billing workflow. No re-architecture, no replacement of your metering or invoicing stack.
Core Capabilities
| Capability | What It Does | API Call |
|---|---|---|
| Emit | Record usage for a customer | POST /api/v1/balance/delta |
| Derive | Compute a running balance from all verified deltas | GET /api/v1/balance/derive/:customerId |
| Compare | Check two balance views before the invoice | POST /api/v1/balance/compare |
| Checkpoint | Create a period-end proof root over verified deltas | POST /api/v1/balance/checkpoint |
How It Works
- Record usage - every time usage accrues or a charge applies, emit a delta.
- Derive balances - PacSpace computes the current balance from verified deltas.
- Compare views - both sides can check the same record before month end.
- Checkpoint the period - create one proof root for the invoice window.
Business data stays private. Proofs can be checked.
Where to Go Next
Pick the path that matches what you're trying to do:
| I want to... | Go to |
|---|---|
| Integrate usage recordation into my app | Balance API |
| Manage my account, keys, and billing | Dashboard API |
| React to record changes | Webhooks |
| Understand proof checking | Verification & Proofs |
| Deploy an autonomous agent | Agents |
| Get running in 5 minutes | Quick Start Guide |