RRetailAgentOS
Scenario: Fresh Corner Market

OPENAI WEBMCP CHALLENGE · LIVE IMPLEMENTATION

RetailAgentOS WebMCP Agent Storefront

The browser agent asks. RetailAgentOS checks what the retailer can actually promise.

WebMCP exposes only the next safe browser action while RetailAgentOS validates inventory, pricing, fulfillment, quote requirements, shopper constraints, and merchant policy.

Start the 90-second demoView source on GitHub (opens in a new tab)Watch video (opens in a new tab)

Choose a native browser-agent mission or the guided replay.

Run the WebMCP demo

Try with a browser agent

Checking for native WebMCP…

  1. Open this page in a WebMCP-enabled browser.
  2. Give the browser agent this mission.
  3. Watch Mission Control update as tools are invoked.
Build a weekend breakfast cart under $30 from Fresh Corner Market using local delivery. Include one dozen Farm Eggs and one Artisan Sourdough Bread loaf. If the Farm Eggs inventory cannot be trusted, show me one merchant-valid substitute, explain the price difference, and wait for my approval. After I approve, prepare the cart for review, but do not check out.

Copying the prompt does not run the agent — it hands the shopper mission to whatever browser agent you connect.

Watch guided mission

No WebMCP agent connected? Watch the complete flow run through the exact same RetailAgentOS handlers, without an external agent.

Shopper & storefront

Farm Eggs, dozeninventory is stale$6.99
Artisan Sourdough Bread, 900g loafdelivery-ready$8.50

Mission Control

Not yet running

The same shared descriptors are used whether an agent or the guided mission invokes them.

State: initialSafe actions exposed: 0

Safe next actions, right now

None registered yet.

Checkout is never exposed

Checkout
  1. Mission received · run the guided mission to see the shared descriptors act.

RetailAgentOS decision

The decision authority, not the agent, exposes the next action.

Shopper approvalPending
Valid pricePending
Current inventoryPending
Cart for reviewWithheld
NOT EVALUATED

Evaluate the shopper mission first.

Why the storefront becomes meaningfully better with WebMCP

Ordinary browser automation

  • Guesses from buttons and product text
  • May act on stale inventory
  • May invent substitutes, prices, or delivery promises
  • May proceed beyond merchant policy

RetailAgentOS with WebMCP

  • Uses typed storefront capabilities
  • Receives deterministic merchant decisions
  • Gets merchant-valid repairs
  • Exposes only the next safe action
  • Never receives a checkout capability in this showcase

Developer evidence

Developer evidence
Storefront: fresh-cornerSession: fresh-corner-1Registration source: no native registration observedRegistry parity: Browser observation unavailableRetailAgentOS-tracked tools: 0Browser-observed tools: unavailable

Each tool descriptor carries an exact name, JSON Schema input, annotations, and lifecycle (registered / invoked / completed / failed / cancelled / unregistered). Native and guided invocations call the identical descriptor handler and RetailAgentOS gateway; only the telemetry source field differs (native vs. replay).

Full event log (0)
[]
One decision, multiple channels
WebMCP

Browser-agent actions demonstrated on this page.

Shipped for this controlled showcase

UCP

Commerce discovery and transaction projection foundation.

Foundation in place

MCP

Remote/client integration path, designed separately.

Designed, not shipped

Storefront UI & feeds

Human and machine projections of the same canonical facts.

Partial — not every channel is live

All of these derive from the same canonical merchant/catalog/policy objects and the same deterministic RetailAgentOS decision — no channel recalculates commerce policy on its own.