Agentic Commerce Protocol (ACP) — how to make your site agent-ready

What it is

Agentic Commerce Protocol is a commerce standard for agents purchasing goods through traditional checkout flows. Unlike UCP (broader, catalog-first) and x402 (micropayment, HTTP-402-first), ACP focuses on the agent-assisted full retail checkout. The discovery convention is /.well-known/agentic-commerce.json.

Remediation Prompt

I want to improve my site's agent readiness. Please implement the following fix for Agentic Commerce Protocol (ACP) across our codebase.

Instructions:
Please fix the Agentic Commerce Protocol (ACP) issue on my site so it is agent-ready.

How we test it

Step	Method	URL
A	GET	`/.well-known/agentic-commerce.json`

Pass Warn Fail Matrix

Condition	Status	Score
Exists with valid schema + endpoints resolve	pass	1.0
Exists but endpoints 404	warn	0.4
404	fail	0.0

Remediation Prompt

If you run an e-commerce storefront, add Agentic Commerce Protocol support.

1. Publish /.well-known/agentic-commerce.json:
    {
      "version": "1.0",
      "provider": "example-store",
      "endpoints": {
        "products": "https://example.com/api/acp/products",
        "cart": "https://example.com/api/acp/cart",
        "checkout": "https://example.com/api/acp/checkout",
        "order_status": "https://example.com/api/acp/orders/{id}"
      },
      "authentication": {
        "type": "oauth2",
        "authorization_server": "https://example.com/.well-known/oauth-authorization-server"
      }
    }

2. Implement the endpoints according to the ACP spec. The flow: agent searches products → creates a cart → initiates checkout → completes via delegated payment → polls order_status.

3. Require OAuth scopes for checkout so the human explicitly grants purchase authority.

Do not enable ACP for high-value purchases without spend limits on the OAuth grant.

References

agenticcommerce.dev

Test Fixtures

pass.json
warn-dead-endpoints.json
fail-404.json