Custos is the treasury operating system for autonomous agents. Every spending rule enforced by the chain, not a server.
Custody. Governance. Settlement.
An autonomous agent that earns and spends without supervision is a small institution. It needs a balance sheet, a chart of accounts, and a constitution. Custos is that constitution, written in code and ratified by the chain.
The reserve is custodial in form, programmatic in function. Each lane is sovereign. Every constraint is verified atomically. Failure is loud, success is invisible. And the ledger holds the receipts forever.
Every movement settles on-chain. No opaque batches, no hidden fees — just the ledger, in real time.
The reserve is the spine. Around it, six instruments compose the grammar of programmable custody. Each is opt-in. Each is composable. Each is enforced by the chain.
Programmable custody
A single reserve contract holds capital under your authority. No key is ever handed to an agent. Movement is bound by code.
Per-agent isolation
Each agent receives its own deterministic lane within the reserve. Its own balance, ledger, and constraint envelope.
Atomic spending rules
Per-transaction maxima and rolling daily caps verified by the runtime. Fail one. The entire transaction reverts.
Approved counterparties
An on-chain allowlist of recipients. Every outbound payment is checked against the roster before it settles.
Time-bounded operation
Transactions live inside windows you draw. The chain's clock is the source of truth. No server, no drift.
Self-healing balances
Lanes refill themselves from the reserve when balances fall below a floor. Permissionless cranks, deterministic targets.
Multi-signer threshold
High-value movements require m-of-n approvals. Proposals expire. Signers are stored on-chain, not in a database.
Your wallet. The only key that configures the reserve.
One contract holds capital. No private key handed to any agent.
Isolated ledgers — one per agent, each with its own envelope.
Governance, roster, hours, replenish, quorum. Enforced atomically.
Server-side rules
Runtime-verified constraints
Trust an operator
Trust the chain
A wallet per agent
A lane per agent
Server dies, agents stall
Rules survive any outage
No counterparty allowlist
On-chain roster, every transfer
No time discipline
Chain clock as source of truth