Agents & Wallets
An agent is any autonomous program that spends or receives money: a coding assistant buying compute, a research agent hiring a legal agent, a shopping bot paying your store.
When you register an agent, Payzor creates three things atomically:
- Identity: a stable
agentId (agent_...) plus a human-readable name.
- Wallet: a ledger balance (USDC-denominated) the agent can spend.
- Audit trail: an append-only log of everything it ever did, with sequence numbers and chained hashes.
How agents get funded
The golden rule
An agent can only move its own money, and only through its own key. There are no endpoints that accept an agentId for spending; if there were, a leaked key would be a master key. The credential is the boundary.
Lifecycle
active: normal operation.paused: policy checks reject new spending; balances untouched.frozen: same as paused, but signals an incident; useful when you suspect a compromised key.
Change status with POST /agents/:id/status. Pausing takes effect on the next policy evaluation; in-flight approved payments complete.
Why wallets matter for businesses
When you receive money from an agent, you know:
- which
agentId paid,
- that its owner’s policy allowed the payment (or a human explicitly approved it),
- and every fact is exportable for accounting via the audit chain.
That is something a card payment from a browser session can never tell you.