# Commerce

Can an agent understand and act on what the site sells?

Prices, availability and the discovery profile that lets an agent transact. Getting this wrong does not degrade quietly: an agent that reads a stale price or an unrecognised availability value quotes something false to a buyer.

| Technology | What it is | Adoption | Status |
|---|---|---|---|
| [UCP profile](/docs/commerce/ucp) | Universal Commerce Protocol discovery for agentic shopping. | Platform default, ▲ rising | scored |
| [Product / Offer schema](/docs/commerce/product-schema) | Price, availability and identifiers an agent can quote. | Web baseline, ► flat | scored |
| [ACP](/docs/commerce/acp) | The Agentic Commerce Protocol, which powered checkout inside ChatGPT. | Early pilots, ▼ receding | watched |
| [AP2](/docs/commerce/ap2) | The Agent Payments Protocol, covering how an agent proves it was authorised to pay. | Early pilots, ► flat | watched |
| [x402](/docs/commerce/x402) | Paying for a request with the HTTP 402 status code, so an agent can settle a charge inline. | Early production, ▲ rising | watched |
| [MPP (Machine Payments Protocol)](/docs/commerce/mpp) | Publishing an API's prices in its OpenAPI document, so an agent knows what a paid endpoint costs before it calls one. | Early pilots, ▲ rising | watched |