Demo Docs Pricing Start Get free accessFree access

Comers · Agentic Commerce

In development

Commerce does not have to start in a browser.

We are building Comers Agentic Commerce so merchants can sell not only through marketplaces and web storefronts, but directly through authorized AI agents and agent platforms — without creating a separate commerce model for machine-driven purchases.

Agentic Commerce is currently in development and is not part of the current Comers release. Free access is for the current Comers platform, not for Agentic Commerce.

  • One checkout foundation for human and agent purchases
  • The merchant stays Seller and Merchant of Record
  • Not Agent Comers — this serves the shopper’s agent
Purchase path · agent surface Target model
  1. Shopper intent
  2. AI agent / platform acts for shopper
  3. Agentic Commerce controlled boundary
  4. Shared Commerce

    ← shared with storefront

    one purchase model

    • Products / offers
    • Inventory
    • Delivery
    • Payment
    • Authorization
  5. Order normal Comers order
  6. Comers operations fulfil · support · returns

01 · New sales surface

A new sales channel. Not a new operational world.

Orders already reach Comers from marketplaces and store platforms. We are building Agentic Commerce to add one more source — external AI agents acting for shoppers — and route it into the same operating model.

  • Marketplace Source
  • Store platform Source
  • Storefront Planned
  • Agentic Commerce In development

One Order

Comers operations

  1. Inventory
  2. Fulfillment
  3. Messages
  4. Support
  5. Returns

An agent-driven purchase should become a normal Comers order — not create a separate AI commerce silo.

02 · One purchase model

Two surfaces. One purchase model.

Comers does not build one checkout engine for people and another for agents. Both surfaces are designed to resolve the same offer, price, stock and authorization rules — and produce the same order.

Human surface

Human shopper browses

Storefront Planned

pages, cart, checkout UI

Shared Commerce

same rules · same checkout foundation

  1. Product / offer
  2. Price
  3. Availability
  4. Delivery
  5. Payment
  6. Authorization
  7. Confirmation

Order one authoritative order

Agent surface

Shopper delegates

AI agent external

Agentic Commerce In development

capabilities, not pages

03 · Authorization

An agent request is not purchase authorization.

In the intended purchase model, an agent can discover products, express intent and prepare a checkout. None of that is permission to buy. The purchase only proceeds once authority is established — and that moment is a distinct, visible gate.

  1. Discover Agent explores offers.
  2. Purchase intent Shopper goal expressed.
  3. Checkout Price, stock, delivery resolved.
  4. Authorization Authority to buy established.
  5. Confirm Purchase confirmed.
  6. Order Authoritative order created.

Ability to request

What an agent can do on its own.

Authority to purchase

What must be granted, and remain attributable.

Authorization contexts · design principles

  • Human confirmed

    agent prepares human approves

    Agent prepares the purchase. Human approves it.

    design principle

  • Bounded delegation

    agent acts within mandate

    Agent operates within an explicit mandate.

    design principle

  • Future autonomous

    agent acts valid explicit authority

    Only where a valid explicit authorization exists.

    future commerce model

04 · Purchase provenance

The order should know how the purchase happened.

A single flag saying an AI was involved answers nothing. Support, returns and disputes need to know which surface was used, what the agent did, and how authority to buy was granted.

source = "AI" Not enough

purchase_context = { surface, interaction, agent,authorization, confirmation }

Purchase context

Conceptual model · not current UI
Sales surface
Agentic Commerce
Interaction
Agent-assisted
External agent
Shopper platform
Authorization
Explicit approval
Confirmation
Human confirmed
Result
Order #10482

05 · Two very different agents

Agent Comers works for the merchant. Agentic Commerce serves the shopper’s agent.

Merchant side Comers operational AI

Agent Comers

Comers’ operational AI. It works inside the merchant’s back office, for the merchant’s team.

  1. Merchant team
  2. Agent Comers
  3. Comers operations

Works with

  • Orders
  • Products
  • Inventory
  • Messages
  • Support
  • Business Instructions

Purpose

Help operate the business

Shopper side In development

Agentic Commerce

A controlled commerce boundary in development that external AI agents, acting for shoppers, would use to buy from the merchant.

  1. Shopper
  2. External AI agent
  3. Agentic Commerce
  4. Shared Commerce

Designed to expose

  • Offers
  • Price
  • Availability
  • Checkout
  • Authorization
  • Order

Purpose

Enable authorized commerce with the merchant

06 · Merchant ownership

Comers does not need to become the marketplace.

Agentic Commerce is not a consumer destination. Buyers find you wherever they already search; Comers is designed to make your commerce reachable and stay underneath as infrastructure.

  1. The merchant remains the Seller.
  2. The merchant remains Merchant of Record.
  3. Comers does not create a global consumer marketplace.
  4. Discovery may happen outside Comers — agents can find merchant capabilities through future distribution mechanisms.

Where discovery may happen

  • AI agent
  • Search
  • Product feed
  • Future agent index
  • Merchant address

Via Agentic Commerce

Your brand

  • Seller
  • Merchant of Record

Comers · infrastructure commerce · orders · operations

07 · Merchant choice

Use the sales surfaces that make sense for your business.

Storefront and Agentic Commerce are intended as independent surfaces. Agentic Commerce does not require a Comers storefront.

    • Storefront Planned On
    • Agentic Commerce In development Off

    Human storefront sales.

    Shoppers would buy on your own storefront. Agents would not be a sales surface.

    shopper → storefront → shared commerce → order

    • Storefront Planned Off
    • Agentic Commerce In development On

    Agent-driven commerce without a Comers storefront.

    Authorized agents would reach your commerce, whatever you use for your website.

    agent → agentic commerce → shared commerce → order

    • Storefront Planned On
    • Agentic Commerce In development On

    Human and agent commerce.

    Both surfaces would use one set of rules, one checkout foundation and one order stream.

    storefront + agentic commerce → shared commerce → order

    • Storefront Planned Off
    • Agentic Commerce In development Off

    Comers as the operational platform.

    No native sales surface. Orders keep arriving from marketplaces and store platforms.

    marketplaces · store platforms → order

08 · Open to evolving standards

Protocols can change. The commerce model should not.

The agent ecosystem is young and its standards will keep moving. Comers is designed to keep them at the edge, behind adapters, so no single external protocol becomes the internal definition of a product, a checkout or an order.

Status

Comers does not currently claim support for a specific Agentic Commerce protocol here. The product model keeps external standards at the edge so they can evolve without becoming the internal Commerce model.

Possible / evolving external protocols

  • UCP
  • ACP
  • MCP
  • Future

Protocol adapters future adapter surface

Agentic Commerce stable capability contract

Shared Commerce internal model · unchanged

09 · Trust boundary

Open to agents. Controlled by the merchant and the platform.

External agents only through the boundary

Controlled commerce boundary

  • Explicit capabilities

    Agents should see only intentionally exposed commerce capabilities.

  • Merchant isolation

    Commerce must remain scoped to the correct merchant.

  • Attributable authorization

    Purchases must preserve how authority was granted.

  • Duplicate safe

    Repeated requests must not create accidental duplicate purchases.

  • Payment boundaries

    Sensitive payment information should remain within approved payment flows.

  • Auditable

    Supported commerce actions should leave attributable operational history.

10 · After the purchase

The agent disappears. The order does not.

Agentic Commerce is meant to change where a purchase can begin — not to fragment what happens once the order exists.

Agent world

AI agent session ends

Authorized purchase provenance kept

Order #10482 · normal Comers order

Comers operations

  1. Inventory
  2. Fulfillment
  3. Shipping
  4. Messages
  5. Support
  6. Returns
  7. After-sales

FAQ

Frequently asked questions

Is Agentic Commerce the same as Agent Comers?

No. Agent Comers is Comers’ operational AI working for the merchant. Agentic Commerce is the commerce boundary in development through which external shopper agents interact with merchant commerce capabilities.

Is Comers creating a consumer marketplace?

No. The merchant remains the seller and Merchant of Record.

Can an AI agent buy anything automatically?

No. Product discovery or checkout creation does not itself authorize a purchase. Purchase execution must follow applicable authorization, approval or delegation rules.

Does Comers support UCP or ACP today?

No. Comers does not claim support for a specific agent commerce protocol. Agentic Commerce is being built to remain protocol-independent, so relevant standards can eventually be supported through adapters.

Does a merchant need Comers Storefront?

No. The product model treats Storefront and Agentic Commerce as independent sales surfaces; Storefront remains planned.

Can I use Agentic Commerce today?

Not yet. Agentic Commerce is currently in development and is not part of the current Comers release yet.

Commerce is changing

Prepare your commerce for buyers that may arrive through an agent.

Comers is building a commerce model where human storefronts and authorized AI agents can use the same products, inventory, checkout and order foundation.

Agentic Commerce · In development