ACP vs MCP
What does the tool mean in the context of commerce?
A tool interface can carry commerce capabilities but does not define an order or checkout by itself. ACP provides commerce-specific semantics; MCP provides general application/tool communication. Ask whether your target integration documents an ACP operation over a supported interface. A generic MCP server badge is not proof of merchant onboarding, checkout or payment capability.
What this establishes
A practical way to inspect evidence and make the next merchant decision.
What it cannot establish
Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.
The overlap
A tool interface can carry commerce capabilities but does not define an order or checkout by itself. ACP provides commerce-specific semantics; MCP provides general application/tool communication.
The merchant decision
Ask whether your target integration documents an ACP operation over a supported interface. A generic MCP server badge is not proof of merchant onboarding, checkout or payment capability.
Where they overlap.
Where they complement.
Compare roles and implementation work. A shared capability does not make two systems interchangeable.
| Decision dimension | ACP | MCP |
|---|---|---|
| Layer | Commerce | Transport |
| Role | Defines commerce interactions; OpenAI also documents structured product feed ingestion. | Provides a way for agent applications to access capabilities and context. |
| Status | beta specification | released |
| Version | 2026-04-17 · repository identifies specification as beta | 2026-07-28 |
| Discovery | Product feeds documented | Tools and resources; not a product feed standard |
| Checkout | Specified; merchant deployment conditional | Only when a commerce tool defines it |
| Payment | Handler integration; not itself a payment network | Not a payment rail |
| Authorization | Integration-specific; confirm chosen flow | Protocol authorization is not purchase intent |
| Transport | HTTP APIs; released repository includes MCP work | MCP transports and messages |
| Adoption | Public spec and partner access docs; store-level use not inferred | Public specification; commerce behavior depends on tools |
| What it does not solve | Does not guarantee ChatGPT placement or automatic merchant approval. | Tool connectivity alone does not define checkout semantics or payment authorization. |
| Evidence | 6 source record(s) Checked 2026-09-28 public-preview; scope-dependent | 2 source record(s) Checked 2026-09-28 live; scope-dependent |
Unknown ≠ unsupported. Announcements and product documentation are not proof of your live integration.
Overlap and replacement risk
These entries occupy different layers. They can work together; replacing one with another may leave a commerce, communication or authorization gap. Keep your source of product truth, fulfillment responsibility and payment obligations explicit.
Go to the source.
Primary documentation records what is publicly stated. It does not independently prove outcomes or your account’s eligibility.
Claim scope: Specification version and scope
Latest stable shown as 2026-04-17; development branch is not a release.
Claim scope: Structured catalog and inventory ingestion for ChatGPT
Claim scope: Product feed access
Approved partners; file and API delivery. This is not evidence of universal checkout availability.
Claim scope: Full snapshot feed delivery
At least daily delivery recommended; not a scanner protocol endpoint.
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: 6b58fb81a436890ede612af94779b0b60a127d95aa0a44b8179d20bb605ca8ea
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: a427ed74696286be7804bb3a4c5dc4c9461b4862da1ed461eeb3e723b03bca9a
Claim scope: Tools, resources, prompts and transport
Claim scope: Version metadata and documented changes only; not merchant adoption.
SHA-256 of retrieved source response: 15e2f46e9f080658c5c25a4e4de6661abc9ab2d90ee56f568c9f6b9620fc0230