Agentic Commerce · UCP
Universal Commerce Protocol
Where the UCP artifacts live and who hosts each one. Everything on specs.agentic.spreedly.com is prerelease and may change; stable releases will freeze under versioned paths.
Business profile
A business publishes this document at /.well-known/ucp, and a platform fetches it during discovery. In UCP, business means merchant. Values marked EXAMPLE_ are placeholders.
Full example
One business profile declaring every handler below, in the exact shape a platform fetches from a business's well-known path.
Where a handler declaration goes
Your business profile is yours: version, name, services, capabilities, and keys are not things to copy from an example. A handler declaration is one entry in your payment_handlers map. Each file below is exactly that entry, ready to merge.
{ "ucp": { ...your version, name, services and capabilities..., "payment_handlers": { "com.google.pay": [ ...the declaration file below... ] } }, "keys": [ ...your signing keys... ] }
Payment handlers
Each handler is a specification, a JSON Schema for its declaration, and an example handler declaration for a business profile. The owner hosts the specification.
Google Pay via Spreedly
Published by GoogleBetaGoogle owns com.google.pay. A business declares it with Spreedly as the tokenization gateway, so Google Pay checkouts charge through the gateway the business already runs.
Spreedly tokenized card
Published by SpreedlyDraftSpreedly-hosted card tokenization as a UCP payment handler: the platform mounts hosted fields, acquires an opaque token, and the business charges it through Spreedly. Identifiers may change before the first stable release.
Protocol
The protocol documents the business profile and handlers above build on.
Universal Commerce Protocol
Published by Open protocolRelease 2026-04-08: the checkout specification the shopping service implements, the REST schema for its endpoints, and the guide a payment handler is written to.