Agent Credit Standard

Identity, amount precision, spending authority, payment challenges and authoritative receipts in the reference protocol.

Identity and units

An AgentID issuer and subject identify an agent. Owner identity is verified separately. One credit has a face value of $0.01; one credit equals 1,000,000 integer microcredits. USD payment requests use integer cents.

Spending authority

Eligible scoped grants, owner caps, accepted payment methods and service offers determine whether a request can proceed. A signed voucher authorizes an agent, an offer, a maximum amount and an expiry. Capturing or retrying a transaction must preserve idempotency.

Runtime payments

A 402 challenge must describe available payment methods and retain the intended transaction. Human approval and successful charge completion are distinct states. Only an authoritative successful receipt permits minting credit and resuming the request. Denied, expired or failed payments leave the request unpaid.

References

Gateway OpenAPI documents the implemented gateway contract. Merchant webhooks documents the implemented signed outbound HTTP contract; delivery requires a verified merchant and enabled owner-configured receiver (integration). GraphQL authoring example demonstrates the renderer and has no GraphQL endpoint. Payment rails report integration status explicitly.