eg

agentic commerce glossary.

84 terms covering AI agents, agent protocols (MCP, A2A, ACP, AP2), agentic checkout, delegated payments, and the identity and infrastructure pieces around them. Every entry links to its primary source.

84 terms

> #

  • 3-D Secure (3DS)

    A card-network protocol (3DS 2.x is current) that lets an issuer authenticate a cardholder during a card-not-present transaction. SCA in the EEA is most often satisfied by a 3DS challenge; agent payments add new metadata (agent identity, mandate references) to the 3DS message.

> a

> b

  • Browser automation

    The use of headless or headed browsers, driven by code or by an LLM, to interact with websites that lack APIs. Common drivers include Playwright, Puppeteer, and Chromium Browser Use; LLM-driven variants include Anthropic's Computer Use and OpenAI's Operator.

> c

> d

> e

> f

> g

> h

  • Human-in-the-loop

    A design in which an agent pauses before taking specified actions and asks a human to approve, reject, or edit the proposed step. Common gates are payment, outbound communication, file deletion, and any irreversible side-effect.

> i

> j

> k

> l

> m

> n

> o

  • OAuth 2.1

    An IETF draft that consolidates OAuth 2.0 best current practice into a single specification, removing the implicit grant and password grant and requiring PKCE for all authorisation code flows. MCP and many agent platforms reference OAuth 2.1 for delegated access.

  • OpenID Connect (OIDC)

    An identity layer on top of OAuth 2.0 that issues an ID Token (a signed JWT) describing the authenticated user. OIDC is the basis of most consumer 'sign in with' flows and is being extended for agents through the OpenID for Agents working group.

  • Operator (OpenAI)

    OpenAI's browser-using agent, introduced in January 2025, that runs in a remote Chromium and completes tasks on websites at the user's instruction. Operator was folded into ChatGPT's Agent Mode in mid-2025.

> p

> r

  • ReAct

    A prompting technique introduced by Yao et al. in 2022 in which the model interleaves Thought, Action, and Observation steps. It became the canonical pattern for tool-using agents before being subsumed by native function-calling in modern model APIs.

    sources:ReAct paper
  • Retrieval-Augmented Generation (RAG)

    A technique that retrieves relevant documents from an external store and concatenates them into the prompt so the model can answer with grounded, cited content. Introduced in a 2020 Meta paper; now standard in customer-support, search, and commerce assistants.

  • robots.txt for AI crawlers

    The application of the Robots Exclusion Protocol (RFC 9309) to AI training crawlers and AI search agents. Most crawlers honour user-agent rules: GPTBot, ClaudeBot, Google-Extended, PerplexityBot, and CCBot are widely declared, while AI shopping agents are now appearing in server logs as distinct user-agents.

> s

> t

> u

  • Universal cart

    A cart format that travels with the buyer across surfaces and merchants, so an agent can compose items from multiple sources before paying once. Bolt, Fast (closed), and Shop Pay have shipped variants; ACP's Cart object is the closest open-spec equivalent.

> v

> w

  • Webhooks

    User-defined HTTP callbacks that a server invokes when an event happens, as opposed to a client polling for changes. Critical in agent payments: the merchant cannot rely on the agent's session staying open, so order paid, refund issued, and dispute opened are delivered as webhooks.

  • Well-known URI

    A reserved URI path under /.well-known/ defined in RFC 8615 for site-wide metadata. Agent specs reuse this convention: A2A serves /.well-known/agent-card.json, OpenID Connect serves /.well-known/openid-configuration, and emerging proposals add /.well-known/ai-plugin.json and /.well-known/agent.json.

    sources:RFC 8615

> z

  • Zero-click commerce

    Purchases completed without the buyer clicking through to the merchant's site, because the agent or interface (ChatGPT, Perplexity, Claude, Gemini) handles cart and checkout in place. The merchant's site never receives a session, and the only artefact is the order webhook.