Agentic Commerce Glossary
Definitive definitions for UCP, ACP, AP2, AEO, GEO, and every term that matters in the agentic commerce era. 20 terms, maintained by Adam Silva Consulting.
Agentic Commerce
Commerce mediated entirely by AI agents acting on behalf of human buyers, without requiring browser sessions or manual interaction. In agentic commerce, AI agents discover merchants via UCP, negotiate and execute transactions via ACP, and authorize payments via AP2 mandates — completing the full purchase lifecycle autonomously. This represents a fundamental shift from human-to-website commerce to agent-to-API commerce.
Agentic Commerce ProtocolsACP (Agentic Commerce Protocol)
The OpenAI-led open standard for AI agent checkout execution, developed in partnership with Stripe. ACP defines the API surface that merchants must expose to allow AI agents to add items to carts, apply promotions, and complete checkout using Stripe Payment Tokens (SPT). ChatGPT Instant Checkout is the most prominent ACP implementation. Without ACP endpoints, AI agents cannot execute purchases in your store — the transaction stalls.
ACP Protocol GuideAEO (Answer Engine Optimization)
The discipline of optimizing digital content and infrastructure to be cited by AI answer engines including ChatGPT, Perplexity, Claude, Google AI Mode, and Bing Copilot. AEO differs from traditional SEO in that it targets AI systems that synthesize answers rather than listing links. Effective AEO requires structured data (JSON-LD), answer-first content format, E-E-A-T signals, and topical authority — the combination that makes AI systems cite your brand as the authoritative source.
AEO Audit ServiceAP2 (Agent Payments Protocol)
Google's cryptographic mandate framework for agentic transactions. AP2 introduces two mandate types — Intent Mandates (for browsing and comparison authorization) and Cart Mandates (for specific transaction authorization) — signed with Verifiable Credentials. AP2 makes agentic transactions legally defensible by creating cryptographic proof of user authorization for every AI-mediated purchase. It is the trust layer that enterprise procurement, compliance, and non-repudiation requirements demand.
AP2 Protocol GuideCart Mandate (AP2)
An AP2 cryptographic authorization type that permits an AI agent to execute a specific, pre-approved transaction on the user's behalf. A Cart Mandate is more restrictive than an Intent Mandate — it authorizes a specific cart (specific items, quantities, and price) rather than general browsing. Cart Mandates are signed with Verifiable Credentials, providing cryptographic proof that the user explicitly authorized the precise transaction the AI agent completes.
AP2 Mandate InfrastructureChatGPT Instant Checkout
OpenAI's consumer-facing implementation of the Agentic Commerce Protocol (ACP), enabling users to complete purchases entirely within the ChatGPT interface without navigating to external merchant websites. ChatGPT Instant Checkout uses Stripe Payment Tokens (SPT) for payment authorization and communicates with merchant ACP endpoints to execute checkout. It demonstrates ACP working in production at scale, and represents the primary demand driver for merchant ACP adoption.
ACP Integration ServiceE-E-A-T
Experience, Expertise, Authoritativeness, and Trustworthiness — Google's quality evaluation framework for content and websites. E-E-A-T signals include author credentials, first-hand experience documentation, third-party citations, industry recognition, and on-site trust indicators (privacy policy, contact information, organizational schema). AI systems use E-E-A-T signals to determine citation worthiness. Strong E-E-A-T is a prerequisite for becoming the source AI agents cite in your topic area.
GEO ImplementationGEO (Generative Engine Optimization)
The practice of optimizing digital content and infrastructure to appear in outputs generated by AI language models and generative search engines, including ChatGPT, Google AI Mode, Perplexity, and Gemini. GEO focuses on structured data coverage, entity disambiguation, topical depth, and content format — ensuring AI models have high-quality, unambiguous information to generate accurate citations. GEO targets the content synthesis layer, while AEO targets the answer retrieval layer.
GEO Implementation ServiceHydration Tax
The performance penalty imposed by client-side React rendering (CSR) on AI agent crawlers and search engines. In a client-side SPA, the server delivers a near-empty HTML shell — JavaScript must execute to render content. AI agents and Googlebot frequently encounter blank pages, index zero products, and generate no citations as a result. The "tax" is the cost paid in discoverability and indexation for choosing CSR architecture. Server-Side Rendering (SSR) eliminates the hydration tax.
Hydration Tax ArticleIntent Mandate (AP2)
An AP2 cryptographic authorization type that permits an AI agent to browse, compare, and evaluate products on a user's behalf without completing a purchase. Intent Mandates are broader than Cart Mandates — they authorize exploratory agent behavior (searching catalogs, checking prices, comparing specifications) but not transaction execution. They are signed with Verifiable Credentials, providing a cryptographic audit trail of user-authorized browsing activity.
AP2 Trust Layer ServiceJSON-LD
JavaScript Object Notation for Linked Data — the W3C standard for embedding machine-readable semantic data in web pages. JSON-LD uses Schema.org vocabulary to describe entities (Organization, Product, Article, Person, Service) and their relationships in a format AI agents and search engines parse without executing JavaScript. Embedded in HTML `<script type="application/ld+json">` tags, JSON-LD is the primary mechanism for communicating structured facts to AI systems that process your pages.
GEO ImplementationSSR (Server-Side Rendering)
The architectural pattern of rendering complete HTML on the web server before delivering it to the browser or crawler. In SSR, every page request returns fully-populated HTML — no JavaScript execution required to read content. AI agents and search crawlers receive complete, parseable content on the first HTTP response. SSR is foundational to agentic commerce readiness: without it, AI agents encounter blank pages, index nothing, and generate no citations. Next.js App Router uses SSR by default.
Case StudiesStripe SPT (Stripe Payment Token)
The payment authorization mechanism used in ACP (Agentic Commerce Protocol) implementations. Stripe Payment Tokens allow AI agents to complete purchases on behalf of users using pre-authorized payment methods stored by Stripe — without the agent ever seeing raw card data. The SPT is generated when a user pre-authorizes AI agent purchasing, and is passed by the AI agent to ACP checkout endpoints to complete transactions. It is the payment primitive that makes ChatGPT Instant Checkout possible.
ACP Integration ServiceToken Efficiency
The measure of how economically a web page communicates useful information to AI agents, expressed as meaningful content tokens divided by total page tokens. Pages bloated with navigation markup, repeated scripts, inline styles, and empty containers force AI agents to process (and pay for) tokens that carry no semantic value. High token efficiency means AI agents extract maximum signal per token consumed — reducing cost and improving citation accuracy. Token efficiency is the agentic-era equivalent of page speed.
Token Efficiency ArticleUCP (Universal Commerce Protocol)
Google's open standard for AI agent commerce discovery, specifying how merchants declare their commerce capabilities in a machine-readable format at /.well-known/ucp/manifest.json. UCP manifests describe what a business sells, how AI agents can query inventory and pricing, which payment methods are accepted, and what fulfillment options are available. AI agents — including Google AI Mode, autonomous shopping assistants, and enterprise procurement agents — use UCP capability profiles to decide which merchants they can transact with. Without a UCP manifest, a business is invisible to AI-mediated commerce.
UCP Protocol GuideUCP Manifest
A JSON configuration file hosted at /.well-known/ucp/manifest.json that declares a merchant's AI commerce capabilities per the Universal Commerce Protocol specification. The manifest specifies the merchant's name, commerce capabilities (catalog browsing, cart management, checkout), supported transport protocols (REST, MCP, A2A), authentication requirements, and product category declarations. Every business seeking AI agent discoverability must maintain a valid, up-to-date UCP manifest — it is the entry point for every AI agent that wants to transact with your business.
UCP Implementation ServiceVerifiable Credentials (VC)
W3C-standardized cryptographic proofs used in AP2 (Agent Payments Protocol) mandate authorization. Verifiable Credentials are digitally signed attestations that can be independently verified without contacting the issuing authority. In the AP2 context, VCs are used to sign Intent and Cart Mandates — creating tamper-proof, cryptographically verifiable evidence that a user authorized an AI agent to perform a specific action. VCs are what make agentic transactions legally defensible and auditable.
AP2 Trust Layer Service.well-known
A standardized URL path prefix (defined by RFC 8615) used for machine-readable discovery files that describe a website's capabilities and configurations. In agentic commerce, three critical .well-known paths are required: /.well-known/ucp/manifest.json (UCP discovery), /.well-known/acp/config.json (ACP checkout configuration), and /.well-known/ap2/mandates.json (AP2 mandate schema). AI agents check these endpoints as the first step in determining whether a merchant is agent-transactable.
Protocol Implementation
From Definitions to Deployment
Understanding the terms is step one. Implementation is step two. Adam Silva Consulting handles the full UCP, ACP, AP2 protocol stack — from manifest files to checkout endpoints to mandate infrastructure.