Agent-commerce readiness

Agent commerce is arriving in two layers. The transaction layer, agents paying on a buyer’s behalf, is gated and still a year or two out for most small businesses, and it will arrive through platforms. The discovery and readiness layer is open now: structured manifests and product feeds that let agents find you and understand what you sell.

SchemaX builds the readiness layer from your verified graph, and it is strict about not claiming more than is true.

The UCP manifest

SchemaX publishes a manifest at the spec-mandated path:


/.well-known/ucp

UCP (the Universal Commerce Protocol) is a site-level JSON manifest that agents can read to learn what a site supports. SchemaX emits an honest-minimal version of it:

your identity (business name and URL) from the grounded Organization on your site;
a pointer to your published schema manifest;
a pointer to your ACP product feed, but only when that feed is actually eligible (see below).

That is the whole declaration. It is intentionally small.

What the manifest never contains: payment handlers, checkout capabilities, cart endpoints, or signing keys. SchemaX does not have those, so it does not declare them, and it cannot declare them by accident. The manifest is validated by a strict schema that rejects any payment or checkout field at compile time. If your business has no grounded identity yet, the manifest is reported as ineligible and the path simply returns a 404 rather than serving something hollow.

Delivery depends on your host. A codebase or the WordPress plugin can serve the well-known route directly. Some site builders cannot serve arbitrary well-known paths today; where that is the case, we say so plainly rather than pretend the manifest is live.

The ACP product feed

ACP (the Agentic Commerce Protocol, from OpenAI and Stripe) defines a product feed that makes your catalog discoverable to AI shopping surfaces. SchemaX compiles this feed from the Product and Offer entities in your verified graph.

This applies to product businesses. A services or content site has no Product entities, so there is no feed to compile, and that is reported as a normal, expected state, not a failure.

For each product, SchemaX maps your grounded facts onto the feed’s required fields: a stable id, title, description, URL, brand, image, price, availability, and seller details. No value is invented and no price or availability is defaulted. If a required field cannot be grounded from your site, that product is left out of the feed and the reason is recorded.

The gap report

The gap report is the part you read. It tells you, product by product, exactly what stands between your catalog and being eligible for agent commerce. For example:

“…is missing a grounded price, so agents can’t quote it.”
“…is missing a product image, so agents can’t show it.”
“…is missing a stable id (sku/@id), so agents can’t reference it.”

A couple of fields the spec requires (target countries and store country) can’t come from a product page; they are merchant configuration. SchemaX flags these as a warning rather than dropping the product, so you see real progress on the grounded fields and a clear note of the configuration to add before you submit a feed.

The gap report is useful even before you can publish anything: it is a concrete, owner-readable checklist of what your catalog needs to be agent-ready.

The no-overclaim policy

SchemaX will not state a capability your business does not have. This is a hard rule across every surface:

The feed’s checkout-eligibility flag is pinned to false. SchemaX never claims a product is directly purchasable through an agent, because that integration does not exist yet.
The feed’s search-eligibility flag is true. The only thing the feed asserts is that your products are discoverable, which is the feed’s entire purpose.
The UCP manifest declares only pointers to real, live SchemaX-served endpoints, never payments, checkout, or cart.
A surface declares your ACP feed only when that feed is genuinely eligible; an empty or ineligible feed is never advertised.

When real checkout rails open to small businesses, this policy is the deliberate place to revisit. It changes only through an explicit decision, never silently.

Owner control

Both the feed and the UCP manifest are off by default. Neither serves publicly until you turn it on for your project. As with every SchemaX surface, nothing goes live without your say-so.