ZOOBC / AGENT TREASURY INFRASTRUCTURE
Give your AI agent money. Keep a ceiling it cannot break.
ZooBC gives autonomous agents room to spend, hire, and transact inside a budget boundary enforced by the network, not by the agent's self-control.
- LIMIT
- Locked up front
- CONTROL
- Human-signed increases
- RECORD
- Independently verifiable
THE UNSOLVED CONTROL LAYER
Autonomy should not require a blank check.
AI systems are gaining their own tasks, tools, and purchasing decisions. The difficult part is giving them financial agency without watching every move. ZooBC turns the spending boundary into network state: the agent can act freely inside it, but cannot rewrite it.
Software proposes. The ledger enforces.
SIX WORKING PRIMITIVES
The control system around an agent wallet.
Start with the allowance. Add approvals, identity, receipts, token rails, and independent verification as the job requires.
An allowance your AI agent cannot exceed.
You do not hand an agent an unrestricted private key. You commit a fixed allowance up front. Raising that ceiling requires a new transaction signed by you, so prompt injection, a software bug, or rogue behavior cannot spend beyond the amount the network has locked.
A payment can wait for you without trapping your money.
An agent can propose a payment that remains pending until you approve it. Every proposal carries a deadline. If no approval arrives, the locked amount returns automatically, without a support ticket or a human remembering to release it.
Agents can hire agents and leave a receipt.
A research agent can hire a specialist agent, pay for a task, and leave both sides with a signed transaction record. The payment and audit trail are independently checkable without reconciling invoices or asking either company for private logs.
Give every agent a signature others can verify.
Each agent can operate with its own cryptographic keypair. It can sign statements about its operator, purpose, and budget, while another agent verifies that the same key authorized the message. Identity claims become portable, signed records instead of editable profile fields.
Settle tiny machine-to-machine payments on-chain.
ZooBC supports ZBC and user-issued tokens traded through an on-chain exchange. That gives agent systems a path to settle small lookups, API calls, or inference tasks without forcing every interaction through card-network economics.
Release payment when independent agents agree.
Place an escrow behind a multisignature approver shared by a panel of agents. A defined threshold, not one gatekeeper, can verify delivery and release payment using the same escrow and multisig primitives already available on the network.
ONE COMPLETE AGENT-TO-AGENT WORKFLOW
A research agent hires a specialist without receiving a blank check.
This is an illustrative workflow assembled from the primitives above. It is not a claim that the complete integration runs automatically without application code.
- 01 / OWNER
Commit the operating budget.
A company funds the research agent's allowance. The committed ceiling defines the maximum value available to that workflow.
→ - 02 / RESEARCH AGENT
Propose the specialist payment.
The research agent selects a summarization agent and creates a payment proposal with an approval deadline.
→ - 03 / SPECIALIST AGENT
Deliver and sign the result.
The specialist returns the work with a signature that ties the response to its cryptographic identity.
→ - 04 / SETTLEMENT
Release or return the funds.
Approval releases the agreed payment. If the deadline passes unanswered, the escrow follows its configured return path.
✓
HOW IT WORKS
Four steps from funding to audit.
- 01
Fund it
Create the account and load the amount your agent may use.
- 02
Set the ceiling
Commit the maximum allowance. Increasing it requires your signature.
- 03
Let it operate
The agent pays, hires, and gets hired inside the boundary.
- 04
Audit anytime
Inspect the transaction history and let unanswered payments return.
HARD QUESTIONS
What the boundary solves and what it does not.
The ledger can enforce financial conditions. It cannot replace careful agent design, identity claims, or result validation.
01Does a spending ceiling make an agent safe?
It limits the amount at risk; it does not guarantee that every purchase is wise. Task permissions, vendor selection, result validation, and operational monitoring still belong in the agent system around the wallet.
02Can the agent raise its own allowance?
Not under the bounded pattern described here. Increasing the committed ceiling requires a new transaction authorized by the account that controls the allowance.
03What happens when a proposed payment is never approved?
A proposal can carry an expiry. If approval does not arrive by that deadline, the escrowed value follows its configured return path instead of remaining pending indefinitely.
04What proves which agent authorized an action?
The cryptographic signature proves that the holder of a particular key authorized the message or transaction. Claims about the operator, purpose, and reputation of that key still need clear signed records and independent verification.
05Is this an agent product or a set of blockchain primitives?
Today the foundation is the ZooBC transaction layer: accounts, signatures, escrow, multisignature approval, tokens, and an auditable ledger. A production agent integration still needs software that assembles those primitives for its specific workflow.
TESTNET IS LIVE
Give your agent a wallet with a boundary.
Fund an experiment on testnet, set the limit, and inspect every transaction the agent makes.