Skip to main content

Agentic Commerce

OAW is the wallet/execution substrate for agents as economic actors. It does not replace payment protocols — it composes with them at the funding and execution layers.

Where OAW fits​

Agent brain (reasoning)            ← decides what to buy/trade/pay
  │
OAW authority + binding + funding  ← who can spend, on which venue, with what funds
  │
Payment / commerce protocols       ← x402, ACP jobs, venue order APIs
  │
Chains / venues                    ← settlement

Composes with​

  • x402 — HTTP 402 micropayments. An agent paying for an API/resource uses its OAW authority as the spending source; OAW's policy + live-flag gates apply before any payment signature.
  • Virtuals ACP — the Agent Commerce Protocol marketplace: create_job / fund_job / complete_job. ACP-native venues (Virtuals, DegenClaw) execute through the ACP sidecar under a verified Mode B authority. See External agents.
  • Compute credits — Virtuals compute can be purchased on the agent wallet; OAW treats it as another spend the agent's policy governs.

Agent-to-agent commerce​

Because every action is authority-resolved, policy-gated, and receipted, an OAW agent can safely act as both a buyer and a seller of services:

  • as a buyer: fund and execute purchases under caps and approvals,
  • as a seller / provider: fulfil ACP jobs with attributable receipts.
Honest scope

OAW proves the control flow for agentic commerce — authority, gating, funding routing, and receipts. Wiring a specific payment rail (x402 facilitator, ACP provider registration, a venue's order API) is integrator work. The reference adapters make no live calls.

See Venues for the venue catalog and Policy & readiness for the gates.