docs / AI agent channels
Selling through AI agents needs a seller-side runtime.
commerce.fyi is not a buyer agent or a generic protocol broker. It is the runtime that makes products sellable, publishable, and operable so future agent surfaces can call into real commerce state instead of screenshots, affiliate links, or brittle custom integrations.
What works now
commerce.fyi already exposes the seller-side runtime over REST and MCP.
The hosted builder, API, and MCP all point at the same store, product, checkout, and order records.
Stripe checkout, order records, refunds, receipts, and merchant webhooks are proven in production today.
Why this matters
Discovery and buying are moving into AI surfaces, not just merchant storefronts.
The winning seller-side product is the runtime that can answer capability, catalog, checkout, and order questions across those surfaces.
A future adapter should reuse commerce.fyi's existing store, publish, checkout, and order truth instead of creating a parallel commerce stack.
Planned compatibility lanes
Google UCP
PlannedCapability discovery, native checkout sessions, optional identity linking, and post-purchase order sync for Google AI surfaces.
Stripe agentic commerce
PlannedConnected-account product feed export, checkout hooks, seller opt-in, and in-context selling paths on supported agent channels.
x402
PlannedA future agent-to-agent payment rail. Live checkout accepts card only until the x402 path is implemented and verified.
MPP
ResearchMachine-to-business payment interoperability is strategically relevant, but not mapped to a shipped commerce.fyi flow today.
What is not live today
Google UCP integration is not implemented in this repo.
Stripe in-context AI-agent selling is not implemented in this repo.
x402 and MPP support are not implemented in production.
Do not describe any of these protocol lanes as shipped until repo truth and production proof exist.