Skip to main content
POST
Provisions the agent’s wallet in the custody plane and persists it. Idempotent — if the agent already has a wallet, the existing one is returned unchanged and no new wallet is created.
Operator only. Provisioning requires an operator credential: a signed-in dashboard session, or an API key minted with the wallet:admin scope. An agent key is refused with 403 (reason: wallet_admin_requires_operator).create, fund, transfer, policy and sweep are the operator surface. An agent spends from its wallet via Pay — it cannot administer it.

Request Body

Fail-closed provisioning

perTxMax is written into the custody plane as a static account policy at create time, which is what makes it survive a compromised agent runtime. If that policy cannot be attached, provisioning fails with 500 internal_error and no wallet is created — there is never a wallet without its cap. Retry the call. Likewise, if the custody backend is unconfigured (BYO CDP credentials absent), the call fails with wallet_not_configured before any row is written.

Errors

CLI

With an explicit custody backend and policy:
This is an operator command — it goes through a signed-in human session. Start one with naive auth session-login, or naive auth google / naive auth email <email> in the browser.

MCP

No MCP tool — deliberately. Wallet provisioning is the operator surface and is not exposed to agents. A wallet an agent can’t reach is the cheapest policy of all.