Conduit logoConduit

Guide

ChatGPT Instant Checkout explained, and where it stops

ChatGPT Instant Checkout lets people (and agent surfaces inside ChatGPT) complete a purchase without leaving the chat. Under the hood it leans on the Agentic Commerce Protocol (ACP) with Stripe in the payment path, a fast, assistant-native checkout for participating merchants.

That is real progress, and for a one-off consumer purchase it is often enough. It is also single-channel consumer commerce: catalog, rails, and merchant set are bounded by what that assistant program allows. Procurement is a different job on a different rail.

What Instant Checkout is

Instant Checkout is OpenAI’s productized path for buying inside ChatGPT. Merchants that participate expose products and a checkout handshake the assistant can complete, and the open standard behind much of that shape is ACP.

For a shopper, the value is obvious: ask for something, see offers, pay without bouncing through a classic cart UI. For a merchant, it is a new demand channel, with the tradeoffs of any garden: participation rules, ranking you do not control, and processor constraints.

What it can and cannot do

Treat Instant Checkout as assistant-scoped commerce, not as "every store on the internet."

  • Can: complete purchases with participating merchants inside ChatGPT’s checkout path.
  • Can: reduce human friction versus browsing storefronts one by one.
  • Cannot (by design): guarantee access to every merchant, every payable rail, or cross-garden ranking on observed delivery.
  • Cannot: replace a procurement agent that must watch supply lines, source across an open supplier set, and track orders under company spend policy.

Why B2B does not run on this rail

This is the part that gets missed, and it is not a criticism of Instant Checkout. It is a statement about which rail it sits on.

Autonomous card checkout is gated almost everywhere. We probed this directly: Shopify reserves it for approved Participating Channels, and drop-ship and distributor APIs require an account opened on the buyer’s behalf plus a prepaid balance no API can top up. Those gates are not bugs. They are consumer payment infrastructure behaving exactly as designed, because the fraud model behind a card assumes a cardholder.

B2B does not buy on cards. It buys on a purchase order against approved terms. UCP already composes with that as a custom payment handler, where the credential is an approved account rather than a card, and AP2 authorizes it rail-agnostically. One human credit approval, then every subsequent order can complete without another one.

So the ceiling on assistant checkout is not the assistant. It is the rail. A procurement agent needs the rail a business actually buys on, plus the ability to compare suppliers it has no prior relationship with.

Where Conduit fits, honestly

Conduit gives any MCP-compatible agent one interface to discover supply across 13k+ merchants, compare on price, delivery reliability, and reputation, then execute or hand off checkout. Money never flows through Conduit.

Full autonomous checkout (mandates, x402, COD, outcome tracking) works today in OpenClaw, Hermes, Cursor, Claude Code, Codex, and similar MCP hosts. ChatGPT Apps are more limited: external checkout requirements and blocked crypto rails mean the full loop is not available there. Developer mode can still attach the MCP for discovery and handoff.

If your goal is "buy this SKU inside ChatGPT," Instant Checkout may well be enough, and you do not need us. If your goal is "know which of my suppliers is about to slip, and have the alternate ready," that is a different product.

If the job is procurement, not shopping

Start where your supply already lives. Connector reads vendors, lead times, on-hand stock, and inbound out of the ERP you run and puts that graph in Hub. Pipes watch those lines and bring you a brief before you would have noticed the drift.

Already self-hosting agents? Connect over MCP and set spend limits so autonomous purchases stay inside caps you approved. Or read the disruption loop for the whole argument in one page.

Frequently asked questions

How can AI agents buy physical goods?
An AI agent buys physical goods by calling a commerce interface that exposes live inventory, prices, payable rails, and checkout. Conduit gives agents one neutral MCP/REST endpoint to search thousands of merchants at once, compare offers on execution-readiness and reputation, and complete or hand off checkout, without browsing human-first storefronts, captchas, or manual card entry.
Can ChatGPT or other AI assistants buy products for me?
Increasingly, yes. Assistants like ChatGPT, Gemini, Copilot, Claude, and Perplexity are gaining checkout through protocols such as ACP and UCP. Conduit gives any such agent one neutral interface to shop across thousands of merchants at once, ranked on the merits, instead of being limited to a single platform’s catalog.
What is ACP (Agentic Commerce Protocol)?
ACP is an open standard from OpenAI and Stripe that powers instant checkout inside AI assistants like ChatGPT. Conduit rides ACP as one discovery and checkout path among many, so an agent is never locked to a single assistant or payment processor.
How is agentic commerce different from traditional online checkout?
Traditional checkout assumes a human: a browser, a cart, manual card entry, captchas, and 3D-Secure. Agentic commerce is API- and protocol-native. An agent discovers normalized supply, decides on price, reliability, and execution-readiness, and completes or hands off checkout in seconds, with no human in the loop unless one is wanted.