Transport protocols
How do stores expose their commerce APIs? Transports define how agents and stores talk to each other.
Transports are one of the four building blocks of the Universal Commerce Protocol. They define how agents reach stores: direct HTTP calls, LLM tool calls, agent-to-agent messages or embedded interfaces. Each transport carries the same capabilities and tools over a different wire protocol.
MCP
Model Context Protocol: the store's UCP operations offered as tools an AI agent calls over JSON-RPC.
Embedded
The store's own checkout, opened in the buyer's browser inside the agent's surface and described with OpenRPC.
REST
Plain HTTP endpoints described with OpenAPI: the store's UCP operations as web API calls.
A2A
Agent-to-Agent: the store runs its own agent, found through an Agent Card, and the buyer's agent sends it messages.
What transport protocols does UCP support?
Four: REST (HTTP APIs described with OpenAPI), MCP (Model Context Protocol, for LLM tool calls), A2A (Agent-to-Agent, through Agent Cards) and Embedded (host-embedded interfaces described with OpenRPC). A store can offer several at once.
Which transport is most common?
Of the stores we check with a valid UCP profile, 97.3% declare MCP, the most of any transport. It depends on the platform: stores offer the transports their platform switches on.
Can a store support multiple transports?
Yes. A store's UCP profile can declare several services, each on a different transport: an MCP endpoint for agents and a REST API for other integrations, for example.
