Skip to main content

​
ACP Quickstart

The fastest path is the scaffolder — it produces a working merchant project with the handler and an embedded commerce engine.

​
Scaffold a project

That gives you a spec-compliant handler plus the embedded iCommerce engine in one container, so a checkout actually reserves inventory and creates an order rather than returning a stub.

​
Or run the handler directly

​
Verify the flow

This walks the complete checkout: create a session, update it, complete it, and confirm an order came out the other side.

​
Check spec compliance

Any ACP handler — yours or someone else’s — can be tested against the spec:
Run the conformance suite before you ship, and again after any change to your checkout logic. It’s the difference between “our handler works” and “our handler is ACP-compliant” — ChatGPT will hold you to the second.

​
The five checkout endpoints

Plus the delegated payment endpoint, POST /agentic_commerce/delegate_payment, which hands a vaulted payment credential to your PSP.

​
Health

GET /health and GET /ready. The readiness probe reports dependency status and returns 503 when a required dependency is unavailable — for example Redis with REQUIRE_REDIS=true.

​
Next

ACP Overview

Concepts and the full flow.

Checkout guide

Conversation to fulfillment.

ACP Guide

Sync Server ACP support.

ICP

The superset protocol.