Help us improve
Share bugs, ideas, or general feedback.
From acp-agentic-commerce
Implements ACP REST checkout API: create, update, retrieve, complete, cancel sessions with state machine, data models, and headers. For merchant endpoints and AI agent flows.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin acp-agentic-commerceHow this skill is triggered — by the user, by Claude, or both
Slash command
/acp-agentic-commerce:acp-checkout-restThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Fetch live docs**:
Implements UCP Checkout REST API: create/get/update/complete/cancel sessions with headers, idempotency, status transitions, negotiation, and error handling. For UCP REST endpoints/clients.
Maps ACP checkout REST operations to MCP tools for AI agents to create, update, retrieve, complete, or cancel sessions via tool-calling in commerce servers.
Implements WebMCP commerce tools for product search, cart management, checkout, returns, subscriptions, and support on e-commerce sites for agentic shopping.
Share bugs, ideas, or general feedback.
Fetch live docs:
https://developers.openai.com/commerce/specs/checkout/ for the canonical checkout specificationsite:github.com agentic-commerce-protocol spec openapi checkout for the latest OpenAPI YAMLhttps://developers.openai.com/commerce/guides/key-concepts/ for data model detailssite:docs.stripe.com agentic-commerce protocol specification for Stripe's merchant-side reference| Operation | Method | Path | Success |
|---|---|---|---|
| Create | POST | /checkout_sessions | 201 |
| Update | POST | /checkout_sessions/{id} | 200 |
| Retrieve | GET | /checkout_sessions/{id} | 200 |
| Complete | POST | /checkout_sessions/{id}/complete | 200 |
| Cancel | POST | /checkout_sessions/{id}/cancel | 200 |
not_ready_for_payment → ready_for_payment → completed
| | |
+──────────────────────+→ canceled ←────+
|
in_progress
|
authentication_required
The five core status enum values are: not_ready_for_payment, ready_for_payment, completed, canceled, in_progress. Note that authentication_required is a transitional/conditional state (returned during 3DS flows), not one of the five core status values.
The merchant controls status transitions. The agent reads the status and reacts.
Authorization: Bearer <token> — REQUIREDAPI-Version: YYYY-MM-DD — REQUIREDIdempotency-Key: <UUID> — REQUIRED on all POSTContent-Type: application/jsonid + quantity (sent by agent in create/update)items_base_amount, items_discount, subtotal, discount, fulfillment, tax, fee, totalAll amounts are integers in minor currency units (cents). $19.99 = 1999. Floating-point is prohibited.
The messages[] array allows merchant-to-agent communication:
The links[] array provides actionable URLs with spec-defined link types:
terms_of_use — Merchant terms of use pageprivacy_policy — Merchant privacy policy pageseller_shop_policies — Merchant shop policies pagenot_ready_for_payment or ready_for_paymentcompleted status + order detailsauthentication_required + authentication challengetype, code, message, paramparam (JSONPath) to indicate which field caused the errorFetch the OpenAPI spec for exact request/response schemas, field types, and all possible error codes before implementing.