Agentic Commerce Protocol (ACP)

ACP is the open standard maintained by OpenAI and Stripe that powers agent checkout (e.g. “Buy it in ChatGPT”). Techfleet implements the merchant-side Checkout API (spec 2026-04-17) so your inventory is reachable from ACP-capable agents using the same tfs_live_… API key.

Endpoints

Base: https://api.techfleet.dev/acp
Authorization: Bearer tfs_live_your_api_key
API-Version: 2026-04-17

POST   /checkout_sessions                 create a session
GET    /checkout_sessions/{id}            retrieve
POST   /checkout_sessions/{id}            update (items / fulfillment / buyer)
POST   /checkout_sessions/{id}/complete   reserve inventory + place order
POST   /checkout_sessions/{id}/cancel     cancel
GET    /feed                              ACP product feed

Create & complete

Amounts are in minor units (cents). Send an Idempotency-Key on complete so retries are safe; inventory is reserved atomically and the delegated payment token is charged before the order is created.

POST https://api.techfleet.dev/acp/checkout_sessions
{ "items": [ { "id": "prod_123", "quantity": 2 } ] }

// → { "id": "acp_…", "status": "ready_for_payment", "line_items": [...], "totals": [...] }

POST https://api.techfleet.dev/acp/checkout_sessions/acp_…/complete
Idempotency-Key: 9f1c…   (UUID v4)
{
  "buyer": { "name": "Acme", "email": "buyer@acme.com" },
  "payment_data": {
    "handler_id": "stripe",
    "instrument": { "type": "card", "credential": { "type": "spt", "token": "spt_…" } }
  }
}

// → 200: status "completed" with an embedded paid order
// → 402: payment declined / not configured — reservations are released, safe to retry

The Stripe shared payment token is charged on the merchant's connected account; Stripe enforces the token's amount, currency, merchant and expiry constraints. See the full API reference and the ACP spec.