— UCP

A3 turns any website into a UCP-compliant commerce endpoint.

The Universal Commerce Protocol gives agents one typed contract — discovery, negotiation, REST and MCP — for transacting with any business. But most suppliers don't expose a UCP API; they expose a website. A3 closes that gap: it learns each supplier's site into deterministic stages, then serves those flows behind a real UCP server.

See the product how A3 closes the gap →
— What UCP is

One protocol for agentic commerce.

UCP is an open specification for how platforms (agents) and businesses transact. It standardises how agents discover a business, call the same commerce operations, and complete payments — without a bespoke integration for each supplier.

"Hermes" — the commerce messenger.
01 · DISCOVERY

Agents can find what a business offers.

Every business publishes a profile that lists its services, capabilities, and how agents should connect — so a platform can discover it without a custom integration.

02 · ONE CONTRACT

The same operations, for tools or APIs.

UCP exposes the same commerce operations to classic clients and to tool-calling agents, so you build the business once and both kinds of callers can transact.

03 · PAYMENTS

Checkout stays safe and separated.

Payment handling is built into the protocol so credentials stay between the buyer’s platform and the business — intermediaries never need to touch card data.

01
— The gap

Most brands sell on a website.

  • UCP gives agents one shared way to discover products, buy, and follow up after purchase.
  • Most hotels, retailers, and travel brands still only have a website — not a UCP endpoint.
What agents need A common shopping contract
  • Find what a business sells
  • Start checkout and pay safely
  • Get a clear confirmation
What most brands have A website built for people
  • Product and search pages
  • Cart and checkout forms
  • Emails and booking references
02
— Bridge

A3 turns the website into a UCP API.

  • In the ADE you define the commerce actions you need — then A3 learns them on the brand’s live site.
  • Those learned journeys are served over UCP, so agents call a standard endpoint instead of scraping ad hoc.
How it works in A3 From brand site to UCP endpoint
  1. 1
    Setup the workflow

    Describe the commerce actions — deals, checkout, book — in plain English.

    Product demo · Setup →
  2. 2
    Learn the brand website

    A3 walks the customer funnel and builds verified stages into a playbook.

    Product demo · Learn →
  3. 3
    Serve it as UCP

    Replay those stages as a UCP (and REST / MCP) endpoint — no LLM at runtime.

    Product demo · Run →
See the full ADE walkthrough on the product page →
03
— Same UCP

To the agent, it works exactly like native UCP.

  • Same discovery profile, same commerce operations, same request and response shape — no special A3 mode for the caller.
  • Whether the brand built UCP into their backend or A3 fulfils it from the website, the agent integration is identical.
For the agent One integration. Two ways to fulfil it.

If it speaks UCP, the agent talks to it the same way — A3 is invisible at the protocol boundary.

Native UCP Brand backend
  • Publishes a UCP profile
  • Exposes deals, checkout, book…
  • Returns standard UCP responses
  • Handles payment per the brand’s own setup
  • Agent integrates once

Fulfilled by the brand’s own systems

A3-powered UCP Learned website
  • Publishes a UCP profile
  • Exposes deals, checkout, book…
  • Returns standard UCP responses
  • Level 1 PCI compliant, with 3DS support
  • Agent integrates once

Fulfilled by replaying the brand’s live site

— Go deeper

UCP is the common language. A3 helps any site speak it.

Read the UCP specification for the open standard, then explore how A3 learns website journeys so agents can shop brands that only have a site today.

UCP spec ↗