Protocols & compatibility

Keep the production path on REST and webhooks. Layer protocols on top only when required.

Pivota supports channel and protocol layers, but they do not replace the default public integration model. External developers should start with API keys, REST endpoints, and webhook delivery, then introduce protocol layers only when a partner program or rollout stage explicitly requires them.

UCP (Universal Commerce Protocol)

Live · self-serve

Hosted seller door, any agent with a portal API key

Pivota runs a hosted UCP seller door: discover it at commerce.mcp.pivota.cc/.well-known/ucp, search and read the catalog with your developer-portal key, add OAuth buyer identity for checkout. Pivota's decision layer is published as the vendor capability cc.pivota.insights.

ACP

Internal beta

Selected technical-partner workflows

ACP is an agent-commerce protocol layer used in selected LLM and partner workflows. Core APIs and webhooks remain the production control surface.

AP2

Internal beta

Selected partner and payment workflows

AP2 is a payment and security protocol layer above standard order and webhook flows. It is not a public self-serve surface in the default developer path.

The default self-serve path remains the core public contract.

Treat REST APIs, API keys, order flows, and webhooks as the production control surface. Standards and protocol layers sit above those operational surfaces and should not be treated as a replacement for them.

First callAuth & webhooks