docs / provisioning

Provisioning

Future packaging for AI-agent surfaces and provisioning tools that need to negotiate commerce capabilities and hand back credentials automatically.

Target provider resource: commerce-fyi/store

Catalog, provision, AI-agent channel negotiation, and credential handoff are planned, not available today.

A provisioned store should use the same store, product, checkout, and order records as the hosted builder and API.

Do not claim Stripe Projects support until it is implemented and verified.

Why this mode matters

Platforms such as Google AI surfaces, Stripe agentic commerce, and future provisioning networks need a seller-side system that can expose catalog, checkout, identity, and order capabilities without rebuilding the merchant's business logic for each channel.

commerce.fyi should adapt the same runtime to future channels rather than creating a separate AI-agent backend.

The provider lane is where catalog discovery, capability negotiation, and credential handoff should land once they are real.

Public positioning can explain why these channels matter now, while keeping every implementation claim proof-gated.

Planned compatibility lanes

Google UCP

Planned

Capability discovery, native checkout sessions, optional identity linking, and post-purchase order sync for Google AI surfaces.

Stripe agentic commerce

Planned

Connected-account product feed export, checkout hooks, seller opt-in, and in-context selling paths on supported agent channels.

x402

Planned

A future agent-to-agent payment rail. Live checkout accepts card only until the x402 path is implemented and verified.

MPP

Research

Machine-to-business payment interoperability is strategically relevant, but not mapped to a shipped commerce.fyi flow today.

Read AI agent channel docs →Read API and MCP docs →Read the agent skill →