KaliCart Bridge · Solution

ACP for WooCommerce

The Agentic Commerce Protocol (ACP) standardizes how an AI agent completes a purchase: checkout sessions, payment tokens, delegated authorization. It deliberately does not standardize how the agent found and understood your products in the first place. That earlier layer — discovery and a readable catalog — is what KaliCart Bridge provides, on your own WooCommerce domain.

What ACP actually covers

ACP is an open standard maintained by OpenAI and Stripe that defines programmatic commerce flows between agents and businesses: creating and updating checkout sessions, passing payment credentials safely, and letting an agent act on a buyer's behalf. Stripe packages it for merchants as the Agentic Commerce Suite, and WooCommerce is a launch partner. If your question is "how does an agent pay", ACP is the answer taking shape.

Checkout protocol, not a discovery layer

Before any ACP checkout session exists, an agent has to answer earlier questions: does this store exist, what does it sell, is this product in stock, at what price, with what variants. ACP assumes those answers are already available. On most WooCommerce stores they are not available in any machine-readable form — which is precisely the gap between being technically able to transact and ever being chosen.

The catalog under the checkout

Bridge publishes discovery documents and a bounded, read-only catalog API from the merchant's own domain: structured search, product lookup, honest price and stock blocks, freshness signals. That is the layer an agent consumes to decide whether to buy, before any protocol decides how to buy.

How the layers fit together

Discovery and catalog: Bridge. Agents find the store, search the live catalog and verify offers from your domain.
Checkout and payment: your WooCommerce flow, and ACP where a platform supports it. Bridge hands off to merchant checkout; it does not sit in the payment path.
No conflict by design. A store can be readable to every agent today and adopt ACP checkout when its platform and payment stack support it. The catalog layer is useful either way — it is what makes the checkout layer reachable.

Why the catalog layer comes first

An agent that cannot read your catalog never reaches your checkout, however standardized that checkout becomes. This ordering is the same argument we made in Before the wallet, there is the catalog: payment protocols compete for the last step of a journey whose first steps most stores have not built. Bridge builds the first steps.

What Bridge does not promise

Bridge does not implement ACP checkout endpoints, payment token exchange or agent-operated purchasing, and installing it does not enroll a store in any ACP-based program. Those capabilities belong to your commerce platform and payment provider. Bridge also cannot guarantee that any assistant will index or transact with a store: it makes the catalog readable and verifiable, which is the necessary condition — not the sufficient one.

Who this solution is for

Merchants and agencies who keep hearing about agentic checkout and want an honest map of the stack: what ACP standardizes, what it assumes, and which layer a WooCommerce store can actually deploy today without waiting for any platform rollout.