Agentic commerce documentation
Let a customer's AI agent find you, book you, and pay once the customer approves. This documentation explains what SOP does and how engineers connect to it.
What this documentation covers
Customers increasingly ask their own AI agent to find a service, pick a time, and even pay. SOP turns a merchant's services, prices and time slots into data an agent can read, and provides booking and payment interfaces, so the agent doesn't have to guess its way around a web page or ask question after question in LINE.
The documentation has three groups: merchants read "Sell to agents"; engineers who build the integration read "Build an agent" and "Concepts and reference". Every page states its status; for features that are not implemented yet, we only describe them and show a flow diagram, with no code.
Steps
- Seller → SOP: Lists services, prices and open slots
- Customer → Agent: Asks for a service
- Agent → SOP: Finds and books (MCP or REST)
- Customer → Agent: Approves the payment
- Agent → SOP: Pays with a payment credential, or a machine payment
- SOP → Seller: Booking and payment; settled as agreed
- Seller → Customer: Provides the service
Where to start
Build an agent
Connect to bookings
Search businesses, check availability, create and manage bookings.
Pay for a customer
Complete a booking payment with a payment credential the customer approved.
Sell to agents
Accept agent bookings
For merchants: what agents can do, where you confirm, how refunds work.
Sell products to agents
Our plan for retail products.
Machine payments
MPP and x402, on testnet only for now.
Concepts and reference
Payment credentials
Shared Payment Tokens, and the three roles: seller, agent and platform.
Business and service data
What the data an agent reads looks like.
Protocols and standards
How MCP, REST, UCP, MPP and x402 map to SOP.
Current status
Status is as of October 22, 2026. There are only three states: Live, Testnet and Planned.
| Feature | Status | Page |
|---|---|---|
| Booking API and MCP (search businesses, check availability, book, change, cancel) | Live | Connect to bookings |
| Online payment when booking (Shared Payment Token) | Live | Pay for a customer, Payment credentials |
| MPP and x402 payment links | Testnet (testnet tokens only) | Machine payments |
| Retail product checkout | Planned (not implemented) | Sell products to agents |
Product feed, /.well-known/ucp, ACP and AP2 | Planned (not implemented) | Protocols and standards |
Who collects payment
Online payments are processed by Seller Tech U.S.A. LLC through Stripe. Fees and settlement timing are stated in the quotation.
Common combinations
| Goal | Pages | Status |
|---|---|---|
| An agent books a service and pays | Connect your agent; Pay for a booking | Live |
| A professional or venue takes agent bookings, with or without online payment | Accept bookings and payments; Payment credentials | Live |
| An agent pays a booking with stablecoins | Machine payments | Testnet |
| A shop sells products inside AI chat apps | Sell products | Planned |