Skip to content

Introduction

PacSpace records usage before the invoice. Both sides can check the same record later.

What this is for

You charge for metered usage: model tokens, GPU-hours, agent-to-agent transactions, API calls. 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

CapabilityWhat It DoesAPI Call
EmitRecord usage for a customerPOST /api/v1/balance/delta
DeriveCompute a running balance from all verified deltasGET /api/v1/balance/derive/:customerId
CompareCheck two balance views before the invoicePOST /api/v1/balance/compare
CheckpointCreate a period-end proof root over verified deltasPOST /api/v1/balance/checkpoint

How It Works

  1. Record usage - as usage accrues or charges apply, emit deltas on the cadence you control.
  2. Derive balances - PacSpace computes the current balance from verified deltas.
  3. Compare views - both sides can check the same record before month end.
  4. Checkpoint the period - create one proof root for the invoice window.

Business data stays private. Proofs can be checked.

What Changes Day To Day

After the wiring, the rhythm is simple. The flush runs unattended on your chosen cadence. Close means locking the period so the invoice references a record that can no longer move. And a challenged number is answered by opening the same record both sides already share, instead of pulling logs. Recordation walks the rhythm end to end, including who on the team touches each step.

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 appBalance API
Manage my account, keys, and billingDashboard API
React to record changesWebhooks
Understand proof checkingVerification & Proofs
Deploy an autonomous agentAgents
Get running nowQuick Start Guide