---
title: "Agentic Commerce Protocol (ACP) · Sitebulb Labs"
description: "ACP lets agents complete purchases on a person's behalf."
url: https://labs.sitebulb.com/docs/checks/commerce/acp/
---

# Agentic Commerce Protocol (ACP)

ACP lets agents complete purchases on a person's behalf.

- Category

  [Commerce](https://labs.sitebulb.com/docs/checks/commerce)

- Standard

  - Emerging checkEmerging
  - Off by default, turn on in settings

## What it checks

ACP defines how an agent completes a checkout for the person it is working for, handing over payment details the merchant can charge.

The extension requests `/.well-known/acp.json` and `/.well-known/agentic-commerce`, in that order, and passes on the first one that returns a non-empty JSON document.

Commerce protocols are new, and most sites have no reason to support them, so absence is **N/A** rather than a failure.

## Results

| Status   | When                                               |
| -------- | -------------------------------------------------- |
| **Pass** | One of the paths returns a non-empty JSON document |
| **N/A**  | Nothing was found                                  |

## How to fix

Publish an ACP descriptor at `/.well-known/acp.json` to support agent-driven checkout. Serve it as JSON (`Content-Type: application/json`); the extension only confirms a JSON document is there and does not validate its contents.

These standards are still settling, so follow the protocol’s own documentation for what the descriptor should contain.
