Request types
Public request families for the commerce layer agents call.
These are the main callable families already exposed through the current public developer contract. They are intentionally grouped by builder workflow rather than by every underlying internal route.
| Request family | Examples | Default path | Why it matters |
|---|---|---|---|
| Authentication and merchant context | GET /agent/v1/merchants | REST with X-API-Key | Validate the key, confirm the branded API base, and establish merchant context before deeper flows. |
| Search and recommendation | MCP search_catalog / get_product / get_alternatives / get_intel | REST / MCP | Resolve products, offers, and merchant data through a structured commerce surface instead of crawling merchant sites. |
| Cart validation | POST /agent/v1/cart/validate | REST (sandbox for writes) | Validate items and cart structure before checkout creation or deeper order flows. |
| Checkout intents | POST /agent/v1/checkout/intents | REST (sandbox for writes) | Create merchant-native checkout flows that carry execution into payment-aware paths. |
| Orders | POST /agent/v1/orders/create, GET /agent/v1/orders | REST | Create and inspect order flows while keeping merchant systems in the execution loop. |
| Order events and execution signals | GET /agent/v1/orders/events | REST | Inspect timeline events and execution state instead of inferring outcomes from front-end surfaces alone. |
| Webhooks | Portal-managed destinations and delivery history (account-scoped contract) | REST + portal-managed lifecycle | Subscribe to events, test delivery, verify signatures, and keep downstream systems aligned after execution begins. |