Skip to content

Agents Glossary

Canonical PacSpace terms for agents. Every term links to the authoritative reference page or endpoint.

This is the terminology source of truth when an agent generates integration code, prompts, or customer-facing copy. Every term below links to the place in the public docs where the concept is fully defined.

Use When

Use this page before writing new integration code, when normalizing copy the agent is about to surface to a tenant, or when disambiguating terms between a prompt and a schema.

Inputs

  • The target integration workflow and the API operations involved.
  • Any existing tenant language that should be normalized to canonical terms.

Primitives

TermDefinitionReference
DeltaA credit or debit change recorded through the API. The fundamental unit.Emit
Verified deltaA delta that has been permanently recorded and can be independently verified.How Verification Works
ProofThe artifact confirming a delta was recorded at a specific time with specific content.Proof Fingerprints
ReceiptA proof document containing one or more verified deltas, safe to share with counterparties.Receipt
FingerprintA unique identifier derived from content. Same content always produces the same fingerprint.Proof Fingerprints
Proof rootA single fingerprint covering every delta in a group or window.Verify
CheckpointA period-end proof that locks verified deltas in a window into one fingerprint.Checkpoint
Derived balanceThe running total computed from verified deltas for a customer.Query

Platform Concepts

TermDefinitionReference
IntegrationA PacSpace environment configured for a tenant. Each integration is an independent verification system.Environments
EnvironmentEither Sandbox (development and testing) or Production (live verified records).Authentication
Sandbox APIDedicated endpoint for pk_test_* traffic. Runs on isolated infrastructure.Authentication
Production APIDedicated endpoint for pk_live_* traffic.Authentication
Configuration IDThe unique identifier for an integration.Environments
Account IdentifierThe unique address for a tenant's data isolation.Tenant Information
Verification layerThe public infrastructure where proofs are permanently recorded. Independent of PacSpace.How Verification Works

Operations

TermDefinitionAPI call
EmitRecord a usage event as a delta.POST /api/v1/balance/delta
DeriveCompute the running balance from verified deltas for a customer.GET /api/v1/balance/derive/:customerId
CompareSurface the exact point of divergence between two parties' views of a balance.POST /api/v1/balance/compare
CheckpointLock a period-end proof covering all verified deltas in the window.POST /api/v1/balance/checkpoint

Public Contract Field Names

When writing schemas, payloads, or SDK code, keep these field names verbatim:

FieldWhere it appearsNotes
recordIdEmit response, status lookupUnique identifier for a submitted delta.
receiptIdEmit and receipt responses, webhooksProof root for the submission. Safe to share.
proofRootCheckpoint, receipt, verify responsesSingle fingerprint covering a group of deltas. Safe to share.
proofHashWebhook payloads, proof responsesThe per-record proof fingerprint. Safe to share.
contentHashWebhook payloads, proof responsesFingerprint of the delta content itself. Safe to share.
previousProofHashWebhook payloadsLinks to the prior proof in the verification chain.
deltaCountCheckpoint, derive, compare responsesNumber of verified deltas in the response's scope.
verificationReferenceDelta status, verify responsesReference on the verification layer for independent verification.

These values appear in public responses and are the fields agents should log, persist, and forward.

Integration Surfaces

TermDefinitionReference
API keyA credential used to authenticate requests. Prefixed with pk_test_ (Sandbox) or pk_live_ (Production).API Key Management
Idempotency keyAn application-supplied value that prevents duplicate effects when a request is retried.Safety and Idempotency
referenceIdThe agent's own deterministic reference for a delta, used for correlation and idempotency.Integration Patterns
WebhookAn outbound HTTP notification sent when a delta is verified or another event fires.Webhook Overview
Autonomous agent patternA webhook handler that reacts to verification data instead of just logging it.Autonomous Agent Pattern

Failure Modes

  • Using prohibited terms from other platforms when writing agent prompts or UI copy.
  • Mixing internal infrastructure language into customer-facing responses.
  • Treating proofHash and proofRoot as interchangeable — proofHash is per record, proofRoot covers a group.
  • Overview — entry point for this section.
  • Capabilities — how the four operations and supporting reads fit together.
  • Authentication — full detail on environment routing and key formats.