What a run supports

What a run supports

The UCP releases, capabilities and transports a run can use, and what the agent and the store settle when the run starts. The tables come from the same settings the runs use, so they change when the runs do.

UCP releases

ReleaseRunsNote
2026-08-25Yes · ours The release our UCP profile declares.
2026-04-08Yes Older than ours, still supported. Calls go out at 2026-04-08, and Info shows it in amber.
OlderNo Send is off and the page says why. A run started by link or the API is refused with the same reason. Inspect can still call the store.
None declaredYesThe run goes ahead.
Newer than oursYes We read the store's profile for the newest release we share, from its supported_versions, and check that profile declares that release. If the store lists none we run, calls go out at 2026-08-25.

When a new UCP release ships, we move to it and the list slides to the new release and 2026-08-25. 2026-04-08 leaves the list once stores no longer rely on it; the changelog says when.

Capabilities

In our UCP profile means our profile at /.well-known/ucp-agent declares it, so it takes part in the intersection with the store's. The agent uses it means negotiation counts it as shared when the store declares it; the agent then calls the store's tools for it.

CapabilityIn our UCP profileThe agent uses it
dev.ucp.shopping.catalog.searchYesYes
dev.ucp.shopping.catalog.lookupYesYes
dev.ucp.shopping.cartYesYes
dev.ucp.shopping.checkoutYesYes
dev.ucp.shopping.orderYesYes
dev.ucp.shopping.fulfillmentYesYes
dev.ucp.shopping.discountYesYes
dev.ucp.shopping.buyer_consentYesYes
dev.ucp.common.identity_linkingYesYes
dev.ucp.common.location.searchYesYes
dev.ucp.common.askYesYes
dev.ucp.common.location.lookupYesYes
dev.ucp.common.payment.termsYesYes
dev.ucp.shopping.purchase_options (draft)YesYes
dev.ucp.food.checkout (draft)YesYes
dev.ucp.food.fulfillment (draft)YesYes
dev.ucp.food.tip (draft)YesYes
dev.ucp.shopping.productsNoWhen the store offers it
dev.ucp.shopping.checkout.embeddedNoWhen the store offers it
dev.ucp.shopping.permalinkNoWhen the store offers it
dev.ucp.common.loyaltyNoWhen the store offers it
dev.ucp.common.payment.authenticationNoWhen the store offers it
dev.ucp.common.payment.split_paymentsNoWhen the store offers it
dev.ucp.common.payment.ap2_mandateNoWhen the store offers it
dev.ucp.lodging.bookingNoWhen the store offers it
dev.ucp.lodging.policy.cancellationNoWhen the store offers it
Note
Draft means merged into the spec but not in a release yet. Its spec page and schema are under the spec's draft.

Transports

TransportWhat a run uses it for
MCP Everything the store's tools offer. Used when the store declares it.
REST The same operations over HTTP: when the store declares REST only, or for one call when MCP fails.
A2A Checkout with the store's agent (A2A 0.3 or 1.0). Search stays on MCP or REST. A2A: the store's agent
Embedded The store's own checkout page, opened for the buyer. Embedded: the store's checkout

What gets settled when a run starts

WhatHow
ReleaseThe newest release both sides run (above).
Capabilities Those both profiles name, each at the newest version both list. An extension counts only if its parent does.
Transport From the services the store declares: MCP, else REST; A2A and Embedded where the store offers them.
Payment The store's payment handlers, from its profile; its answer on each checkout decides.
Identity Our UCP-Agent profile on every call, and a signature on state-changing calls from the keys in our profile. Identity Hub
Buyer account Account linking, when the store declares identity linking. Agent identity

A run's Discovery and negotiation tab shows what was settled for that run.

Something wrong on this page?