ACP Overview

The Agentic Commerce Protocol (ACP) lets AI agents discover and purchase products and services from your Chipp app. Instead of requiring a human to browse a website, an external agent can programmatically find what you offer, create a checkout session, and complete a purchase — all through a REST API.

How It Works

ACP follows a four-step flow:

1. Discovery     Agent fetches your product catalog
                 GET /acp/{appId}/products

2. Checkout      Agent creates a checkout session with selected items
                 POST /acp/{appId}/checkout_sessions

3. Payment       Agent completes the checkout, triggering payment
                 POST /acp/{appId}/checkout_sessions/{id}/complete

4. Fulfillment   Order is created, fulfilled, and webhook fires
                 Your webhook endpoint receives order details

Two Access Modes

ACP supports two ways for purchases to happen:

External API (agent-to-agent) — An external AI agent (ChatGPT, Perplexity, a custom agent) discovers your product catalog via the REST API, creates a checkout session, completes it, and receives the result via webhook.

In-chat checkout — A consumer chats with your agent. When the agent invokes a priced tool, the system shows an inline Stripe checkout card. The consumer pays, the tool executes, and the result is delivered in the conversation.

Both modes use the same underlying infrastructure. This documentation covers the external API mode.

Getting Started

1. Publish Products

In your app’s builder, go to Launch > Monetize and open the Catalog tab, then create products. Each product has a name, optional SKU and description, a price in cents, a currency (USD, EUR, or GBP), and a fulfillment type. Checkout charges in the product’s currency.

For Automatic fulfillment, pick a Bound tool from the tools connected to your agent (and optional JSON tool parameters). After payment, your agent runs that tool and returns the result on the order. Without a bound tool, or with Manual fulfillment, the order waits as confirmed for you to fulfill it.

2. Create an ACP API Key

In the API Keys section of the same Catalog tab, create an API key with a label (for example “Production”). You’ll see the raw key once — copy it and store it securely. The key has the prefix acp_.

Click Webhook on the key to set the HTTPS URL that receives order events and a signing secret. See Webhooks.

3. Discover and Purchase

Use the key to authenticate checkout operations. Product discovery endpoints are public and require no authentication.

Base URL

All ACP endpoints are scoped to a specific application:

https://build.chipp.ai/acp/{appId}

Replace {appId} with your application’s UUID.

Endpoint Summary

Public (no authentication)

Authenticated (Bearer token)

What’s Next

• Authentication — How to authenticate API requests
• Agent Discovery — Product discovery endpoints
• Checkout — Creating and completing purchases
• Webhooks — Receiving order notifications