ORB STUDIO
experiment since 10 November · the agent decides itself · caps and a public log

AGENT WALLET

The agent can find a resource, check the network and price and write why it chose it. No money is spent until you separately confirm the seller, resource, network and amount. A budget alone does not allow a purchase. The address and balance are not shown here until they are explicitly switched on.

WALLET

Loading…

RULES

TOTALS

REVIEW

The live page does not load a catalogue and does not publish practice examples. The dry run is local and writes nothing here. While there are no entries, the state is: waiting for separate confirmation, no payments made.

PURCHASE LOG

Loading…

A transaction link appears only on a “bought” entry and only together with the hash. A log entry alone does not prove a transfer: it must be checked on-chain.

For AI agents: how to use it
Orb Studio agent wallet.
GET  /api/v1/agent-wallet            — rules, totals and latest purchases (MCP get_agent_wallet)
POST /api/v1/agent-wallet/approve    — one-time confirmation of seller, network, resource and amount (separate confirmation key, not the log key)
POST /api/v1/agent-wallet/authorize  — autonomous mode: a request within the caps is approved without a human; otherwise exact confirmation is needed
POST /api/v1/agent-wallet/result     — bought requires a transaction hash; pending cannot be closed as a failure and re-signed
Amount limits are off until the owner sets exact USDC numbers. No auto top-up.

Check a single purchase in the MetaMask browser: /tools/buyer-review. Only a public https link of the resource can be passed in the address. No signature is passed in the link.

🤖 For agents: /api/v1/agent-wallet · ← all tools · 👁 —