UCP Playground docs
How to point the Playground at a target, drive a model against it, and read a result you can hand to a merchant.
Start herefive minutes
Everything else
01Test a storePoint the harness at a store: inspect tools by hand, run real agents, save targets.
02Test your agentThe other side of the handshake: validate your agent against live reference stores.
03AutomateThe same harness, headless: API, collections, schedules, assertions, webhooks, CI.
04Test locallyStores on your own machine — tunnels today, the Local runtime next.
05ConformanceWhat the verdicts mean: schema quality, identity enforcement, funnel outcomes, scoring.
06Be testedFor merchants: make your store agent-ready and verify who is calling it.
07WorkspaceTeams, roles, scoped API tokens, and usage.
08ReferenceThe precise layer: glossary, API contract, error shapes.
09TroubleshootingWhen something breaks: common errors, OAuth, transports.
Take the harness with youA Chrome side panel that runs a session on the tab you're on — the storefront beside what the agent actually received.
chrome side paneldetects /.well-known/ucppersonal access token
Spec, not productThe protocol itself is documented separately — transports, schemas, and the identity profile.