Skip to main content
Who this is for: a commerce platform or agent host that connects customers to merchants. A UCP client reads a profile before it connects to anything: which services a business speaks, over which transport, at which endpoint, and which capabilities those endpoints implement. A storekit ordering host publishes that profile, and the endpoints it names are the customer-facing MCP endpoints.

Paths

One host sells for many venues and each has its own MCP endpoint, so the host profile lists them — capped at 25, like every other agent-facing list — and an agent already talking about a venue reads the venue path instead. Which venues appear comes from the host itself, so a brand on its own domain advertises that brand’s locations and nothing else. Responses are JSON, cached for 15 minutes and open to any origin. A host with no venues, or a venue slug that does not resolve, is a 404: no profile beats a profile with no endpoint in it.

Profile

Each declared endpoint answers a GET probe with 200, and the ordering host’s robots.txt names the agent crawlers so the well-known path is unambiguously allowed to them.