Open Agent Wallet
Open Agent Wallet (OAW) is a vendor-neutral standard + reference SDK for the hardest part of building AI agents that are autonomous economic actors: giving an agent one wallet authority, binding it to many trading venues, funding it across chains, and letting it act from a chat surface without prompt injection moving money.
It is not a wallet provider and not an exchange. It is the missing glue — with first-class adapters for Privy (embedded / server / agent wallets + chain-agnostic deposit addresses) and Virtuals.io (EconomyOS / ACP / DegenClaw / tokenization), so you can use the rich Virtuals agent wallet without its three-chain limit.
The LLM / agent brain reasons and proposes actions. The backend executor owns signing, policy, approval, live flags, and receipts. The brain never holds a key.
What OAW gives you
| Pillar | What it means |
|---|---|
| One authority | One AgentAuthority per agent. A Privy agent wallet (Mode A) or a linked Virtuals wallet (Mode B) are two implementations of the same thing. |
| Plug-and-play venues | Add a venue with data + one adapter — not a rewrite. 7 reference adapters ship today (EVM and non-EVM). |
| Cross-chain funding | "Deposit USDC anywhere → fund the venue." Chain-agnostic deposit addresses, any-chain bridges, swaps across the CAIP-2 set. |
| Safe from chat | Reasoning-based intent + deterministic, policy-gated execution. Prompt injection can't move money. |
| Honest by construction | Every shipped adapter is a reference adapter — it proves the control flow but makes no live venue call until wired. |
The operating model
The decisive question, resolved
Can a developer backend create a Virtuals/EconomyOS agent wallet headlessly?
No server-side creation surface is verified today — the verified ACP client exposes
verify_identity / signer_status / verify_authority_proof / create_job / dgclaw_*
but no create_agent. So OAW ships two production modes (A: provider-managed, B: link
an existing Virtuals wallet) and proposes the convergence path to Privy and Virtuals. See
Agent authority.
These docs describe the SDK's control flow and contracts. Every venue adapter is a reference adapter: it does not make a live venue API call until an integrator wires the real venue SDK. Live money movement is off by default. See Capability status.
Start with Getting started, or jump to Agent authority — the heart of the design.