Financial control for autonomous agents.
Give agents a budget, not your private keys. Treasury Copilot turns an agent payment request into a bounded, policy reviewed, auditable outcome.
Owner permission
THE GAP
Agents can reason. Their spending authority is still unsafe.
Useful agents will need to buy APIs, data, compute, software, and services. A funded private key creates unrestricted exposure. Manual approval for every small payment removes the point of autonomy.
Treasury Copilot puts a policy boundary between agent intent and irreversible execution.
THE PAYMENT JOURNEY
One request. Four control states.
From owner delegation to an auditable settlement, every step is explicit.
Current step: Owner permission
Owner permission, agent identity, policy limits, and a scoped API credential.
The agent submits recipient, amount, category, justification, and optional evidence through HTTP.
GenLayer determines whether the request satisfies the owner's policy and evidence requirements.
Approved execution and the final transaction hash remain available in the audit trail.
REGISTER THE AGENT
Define authority before the first request arrives.
The owner connects a wallet, grants bounded USDC permission, binds one agent to one policy, and receives a scoped `tcp_` credential.
Open owner setupDEVELOPER EXPERIENCE
Agents integrate with JSON, not wallet infrastructure.
The platform handles GenLayer submission, policy binding, finality, execution, and audit history behind a stable HTTP interface.
Explore the Agent API{
"agent_address": "0xRegisteredAgent...",
"recipient": "0xApprovedMerchant...",
"amount": "12.50",
"category": "infrastructure",
"justification": "Monthly deployment service",
"idempotency_key": "deploy-2026-08"
}THE TRUST BOUNDARY
Useful autonomy without unrestricted custody.
The agent can ask. The policy decides. The owner can stop it.
No agent private keys
Agents authenticate through scoped API keys that identify them but never sign blockchain transactions.
Every request reviewed
Deterministic checks and GenLayer prompt comparative review evaluate every valid payment request.
Owner controlled revocation
Owners retain custody, policy control, API key rotation, and the ability to stop future execution.
THE AUDIT TRAIL
Every decision leaves evidence.
Request identity, policy version, verdict reasoning, execution state, and the final transaction hash remain available for review.
THE NEXT CONTROL PLANE
As agents become economically active, policy becomes infrastructure.
Wallets handle custody. Payment networks handle settlement. Treasury Copilot governs why an agent is allowed to spend and records what happened.
Give your agents a budget, not your treasury.
Connect an owner wallet, grant bounded spending permission, define the policy, and issue an agent API key.