Skip to main content
UCP (Unified Commerce Protocol) is Sly’s native protocol for tokenized commerce. A merchant issues a UCP token representing an order; a buyer (human or agent) exchanges the token for settlement. UCP is the fallback / bridge protocol — if you don’t know which protocol a merchant speaks, assume UCP.

Why UCP

  • Rail-agnostic — same token can settle via stablecoin, card, ACH, wire, or on-chain
  • Human-and-agent compatible — works for both AI buyers and traditional checkout
  • Discoverable — merchants publish their capabilities at /.well-known/ucp
  • Programmable — settlement rules, windows, and reconciliation built in

Anatomy

Create a UCP token (merchant side)

Response:
Return the token to the buyer.

Settle a UCP token (buyer side)

Response:

Key endpoints

Settlement rules

Merchants can define rules that automatically route or split settlements:
See the API reference for the full rule grammar.

Discovery

Merchants publish their UCP capabilities at a well-known URL:
Returns JSON describing accepted rails, currencies, categories, and settlement windows. Agents use this to decide whether and how to transact.

When to use UCP vs. others

  • Use UCP when the merchant wants flexibility on settlement rails (stablecoin OR card OR ACH) or needs programmable fee splits
  • Use ACP or AP2 when integrating into Stripe/OpenAI or Google ecosystems specifically — those protocols are prescribed for those marketplaces
  • Use x402 when the purchase is per-API-call micropayment
  • Use A2A when the purchase is from another AI agent
UCP is the most general of the six; start here if you’re unsure.