The Financial OS for the Agent Economy
Give your agents a financial OS in 30 seconds.What Agents Can Do With AgentaOS
Transact Autonomously
Agents spend money under human-set guardrails. Spending caps, approved vendors, business hours, DeFi slippage protection — all enforced before every transaction. Humans set the policy. Agents execute within it.
Get Paid for Services
Agents advertise capabilities and accept payments. One link. Instant settlement. Customers — human or AI — pay and the agent delivers. No invoicing, no chasing.
Hire Other Agents
An agent that needs a capability it doesn’t have can pay another agent to do it. Agent-to-agent commerce via the x402 payment protocol. Agents compose into teams, each billing for their work.
Know Their Master
Every agent has a delegated identity — it knows who created it, what organization it belongs to, and what authority it operates under. Provable, on-chain, auditable.
The core guarantee: The full private key never exists. Not in memory, not in logs, not anywhere. Three shares. Any two sign. The key itself never materializes. This is the foundation — sovereign accounts that no single party can compromise.
The Bigger Picture
Today’s agents are powerful but economically powerless. They can research, analyze, and generate — but the moment money is involved, a human has to step in. That’s a bottleneck. AgentaOS removes it. When agents have their own financial identity, they can:- Operate under policy, not permission. Instead of asking a human to approve every transaction, the agent follows pre-set guardrails. Humans define the rules once. Agents transact freely within them.
- Earn, not just spend. An agent that can accept payments can offer services — data analysis, content generation, code review, monitoring. It advertises a capability, quotes a price, and collects payment on delivery.
- Compose into teams. A coding agent needs a testing agent. A research agent needs a summarization agent. With x402 payments, agents hire each other directly. One agent’s output is another agent’s input, and money flows alongside the work.
- Prove who they represent. A delegated identity ties every agent to its creator. When an agent transacts, the counterparty knows who’s behind it — which organization, which authority, which rules. Trust is cryptographic, not assumed.
How It Works
Every agent account starts with key setup — 3 shares are created. The full key never exists. Any 2 shares can sign together. Why threshold signing? Because the moment you store a private key somewhere — a file, an HSM, a vendor enclave — it becomes a target. AgentaOS never creates the key in the first place. Three shares exist independently. Two cooperate to sign. The key itself is a mathematical construct that is never materialized.Signing is a multi-round protocol. Two parties exchange messages over HTTPS and produce a valid ECDSA signature together — without either one seeing the full key. No single share can do anything alone.
Three Signing Paths
| Path | Shares Used | When |
|---|---|---|
| Signer + Server | Signer share + Server share | Normal autonomous operation. Agent runs 24/7. Guardrails enforced. |
| User + Server | Passkey-encrypted share + Server share | Dashboard manual signing. Human-in-the-loop. |
| Signer + User | Signer share + User share | Server down. Emergency bypass. |
The Stack
| Layer | Component | What It Does |
|---|---|---|
| Interface | Dashboard | Create accounts, set guardrails, accept payments, sign manually |
| CLI | agenta | Terminal tool — create signers, send transactions, deploy contracts |
| SDK | @agentaos/sdk | TypeScript library for any Node.js app, AI agent, or framework |
| AI Bridge | MCP Server | Give Claude, Cursor, or any AI assistant access to agent accounts |
| Payments | x402 Protocol | Agent-to-agent and human-to-agent payment protocol |
| API | REST API | Signing sessions, signer management, guardrails, audit logs |
Key Capabilities
Sovereign Accounts
The key never exists. Not as a variable, not in memory, not in transit. Math enforces this, not policy. No vendor can freeze your agent’s funds.
Guardrails
15 guardrail types. Spending limits, daily caps, allowlisted contracts, blocked addresses, rate limits, time windows, slippage protection. All enforced before every signature.
Accept Payments
One link. Customers and agents pay instantly. Funds settle in under 1 second. No crypto knowledge needed.
Agent-to-Agent Payments
Agents hire other agents via x402. An agent that needs a capability pays for it. Composable agent teams with real economic incentives.
Delegated Identity
Every agent knows who created it and what authority it operates under. Provable ownership. Auditable delegation chain.
Open Source
Open source SDK, CLI, and core libraries. Apache-2.0 licensed. Read every line. Audit the cryptography yourself.