ComOS Is Live: The Commerce Layer for AI Agents

Ronald Reynolds · 2026-02-10 · 5 min read

Today we're launching ComOS Gateway — the commerce control plane for AI agents.

If that sentence isn't immediately clear, here's the short version. AI agents — Claude, ChatGPT, Gemini — are learning to transact. They speak a handful of open protocols (MCP, UCP, ACP, A2A) to discover catalogs, build carts, run checkouts. If a merchant's storefront doesn't speak those protocols, the agents can't see it. Not "ranks poorly." Invisible.

ComOS is the answer to that, and it's a different shape than the answers most of the industry is building.

ComOS is unified and federated. Shopify is fragmented and isolated.

Unified inside: one operating system, no app seams. Federated outside: one endpoint, every merchant on the network. Operating systems are by definition both. Platforms — Shopify, WordPress + WooCommerce, the rest — are neither. That architectural difference is the whole story, and it's why agents shopping on the ComOS network behave like they're shopping on a single, coherent layer instead of a thousand bolt-on integrations.

One connection. Every AI agent. Every merchant. Live today. What's Live

ComOS Gateway is a single federated endpoint that connects AI agents to merchant storefronts. An agent connects once and gets access to every merchant on the network — search, cart, checkout, orders, inventory, returns, support.

As of today: A federation gateway exposing the full commerce control plane to MCP, UCP, ACP, and A2A agents 100% platform coverage from the gateway — every REST path on the ComOS platform is reachable through one agent connection Sub-100ms agent execution times at p95 Per-tenant circuit breakers, OAuth 2.1 with PKCE, enterprise SSO compatible (Okta, Azure AD, any OIDC provider) Live end-to-end agent checkout: search → cart → shipping selection → payment session

This isn't a beta or an MVP. It's a complete operating system for commerce — three integrated systems, dozens of microservices, dozens of autonomous agents running the operation. Production-grade error handling. Comprehensive test coverage. Built to the standard commerce infrastructure demands.

Update, May 2026: since this post went live, ChatGPT and Claude can both shop the ComOS merchant network end-to-end. Custom GPT is live at chatgpt.com. Claude connects through the MCP connector. The "ask the agent to shop" demo is now a working flow, not a roadmap slide. Three Doors, Not a Migration

Every merchant on a legacy platform has heard the same pitch a hundred times: rip-and-replace, eighteen-month engagement, six-figure consulting bill, hope it works.

We don't open with that.

Door 1, in 24 hours: we put an MCP and UCP endpoint on a merchant's existing catalog. Their store doesn't change. Their checkout doesn't change. But every major AI agent in the world can now find their products and add to a cart. Zero risk. The legacy stack is untouched.

Door 2, in about a week: we stand up a ComOS storefront at a staging URL, mirroring the same catalog. The merchant can compare side by side — agent-native chat, native checkout, the works — without a single customer affected.

Door 3, in minutes: flip DNS. Humans land on ComOS. The legacy platform retires. A three-month migration replaced by a DNS change, because the proof was built in the first two doors before the commitment was asked for.

That's the structural answer to "but my whole business is on WooCommerce / Magento / Shopify." We don't argue with the existing stack. We make the new layer additive until the merchant decides it's ready to be primary. Why This Matters Now

MCP became a Linux Foundation standard. That's the same institutional backing as Linux and Kubernetes. Adoption isn't a question of if anymore — it's a question of how fast.

The market data is already in the open: Roughly a quarter of US consumers made AI-assisted purchases last year AI influenced billions in Black Friday spend McKinsey projects agentic commerce in the trillions globally by 2030 The vast majority of small and mid-market merchants have no agent-protocol presence at all

That last point is the gap ComOS exists to close. Enterprise brands have the budgets and engineering teams to build their own MCP servers and protocol stacks. The hundreds of thousands of merchants in the $1M–$20M range don't — and they're about to be invisible to the fastest-growing channel in commerce history.

Not because their products aren't great. Because they don't speak the protocol. What Agents See

When an agent connects to the ComOS Gateway, it doesn't see a directory of stores. It sees a single, coherent commerce surface — every merchant exposed through the same set of tools, the same scopes, the same auth flow. Search across the network. Build a cart against any merchant. Run a checkout. Track an order. All one endpoint.

That's federation. It's how the internet works (one HTTP, billions of sites). It's how Visa works (one network, millions of merchants). It's how operating systems work (one kernel, every device). And it's the shape commerce needs in order for an agent ecosystem to function at scale — because agents are a commodity, but the network they shop on isn't.

We built the network. Where We're Going

Door 1 onboarding is live for any merchant that wants agent visibility on their existing stack in 24 hours. Door 2 storefronts are live for the merchants who want to see the full ComOS experience before they commit. Door 3 — DNS flip to a new operating system — is open for the ones who've decided.

If you sell online and you're not yet visible to AI agents, that gap widens every week. We built ComOS to close it without asking you to bet the business on a migration.

Welcome to agentic commerce.