Glossary

Plain-English definitions of the terms behind AI agents, agent payments and bot verification.

  • Agent cardAn agent card is a JSON document, defined by the Agent2Agent (A2A) protocol, that describes an AI agent: its name, what it does, the skills it offers, where to reach it and how to authenticate. Other agents read it to discover what the agent can do. It is usually published at /.well-known/agent-card.json and can be digitally signed.
  • Agent mandateAn agent mandate is a digitally signed record of what a person has authorized an AI agent to do, such as which item to buy and at what price. In Google's AP2 protocol, mandates are described as tamper-proof, cryptographically signed contracts that serve as verifiable proof of the user's instructions.
  • Agent Payments Protocol (AP2)The Agent Payments Protocol (AP2) is an open protocol for payments made by AI agents. It records what the user authorized in signed mandates, so a merchant or payment provider can check that a purchase matches the user's instructions. Google announced it in September 2025 and contributed it to the FIDO Alliance in April 2026.
  • Agent registryAn agent registry is a published list of known AI agents, usually with each agent's public signing keys or a link to them, that websites and payment networks use to recognize agents they trust. Examples include the key directories Visa and Mastercard host for their registered agents. There is no single global registry.
  • Agent2Agent (A2A)Agent2Agent (A2A) is an open standard for AI agents to discover, communicate and transact with each other. Each agent publishes an agent card describing who it is, what it can do and where to reach it. Google originally developed A2A, and it is now stewarded by the Linux Foundation.
  • Agentic AI Foundation (AAIF)The Agentic AI Foundation (AAIF) is a foundation under the Linux Foundation that gives open-source AI agent projects a neutral home. It was announced on December 9, 2025, with three founding projects: Anthropic's Model Context Protocol (MCP), Block's goose and OpenAI's AGENTS.md.
  • Agentic checkoutAgentic checkout is a purchase that an AI agent completes on a shopper's behalf, either inside an AI assistant or by acting on the store's own site, instead of the shopper filling in the checkout pages themselves. The shopper usually confirms the order, and the store stays the seller.
  • Agentic commerceAgentic commerce is shopping where an AI agent finds products, compares options and sometimes completes the purchase for a person. The shopper gives the agent a goal, and the agent does the browsing and buying within limits the shopper has set.
  • Agentic Commerce Protocol (ACP)The Agentic Commerce Protocol (ACP) is an open standard, created by OpenAI and Stripe and now also maintained by Meta, that defines how an AI agent checks out with a business and passes a payment credential to it. The business keeps the customer relationship as the merchant of record, and the spec is versioned by date.
  • Agentic tokenAn agentic token is a card-network token issued for purchases an AI agent makes, so the agent can pay with a customer's card without handling the real card number. Mastercard introduced Agentic Tokens with Agent Pay in April 2025, building on the tokenization already used for contactless payments and saved cards.
  • AGENTS.mdAGENTS.md is a plain Markdown file placed in a software repository that gives AI coding agents project-specific instructions, such as how to build, test and style the code. OpenAI released it in August 2025, and it is now stewarded by the Agentic AI Foundation under the Linux Foundation. It is not a file you publish on your website.
  • Cart MandateA Cart Mandate is a signed record, in Google's original design of the Agent Payments Protocol (AP2), of the exact items and price approved for an AI agent's purchase. The shopper signs it when approving a cart, or the agent generates it under an earlier Intent Mandate. The current AP2 documentation describes the same step as a closed Checkout Mandate.
  • ChatGPT WalletChatGPT Wallet is OpenAI's payment feature that lets a ChatGPT user's AI agent pay on a business's website with the user's card. The customer reviews and approves each purchase in ChatGPT, the merchant receives a network token instead of the full card number, and the merchant's existing checkout processes the payment.
  • Content signalsContent signals are a line in robots.txt that states how a site owner wants its content used once it has been accessed, using three signals: search, ai-input and ai-train, each set to yes or no. Cloudflare introduced the Content Signals Policy in September 2025. The signals express preferences and do not technically block anything.
  • EU AI ActThe EU AI Act is Regulation (EU) 2024/1689, the European Union's law on artificial intelligence. It bans a short list of AI practices, sets strict rules for high-risk AI systems, adds transparency duties for AI that talks to people or generates content, and regulates general-purpose AI models. Its rules apply in stages, and the Digital Omnibus on AI (Regulation (EU) 2026/1744) moved the high-risk dates to December 2027 and August 2028.
  • HTTP 402 Payment RequiredHTTP 402 Payment Required is an HTTP status code that the HTTP standard reserves for future use without defining how it works. Newer payment protocols, including x402 and the Machine Payments Protocol (MPP), and Cloudflare's pay per crawl use it to tell a client, often an AI agent or crawler, that it must pay before the server returns a resource.
  • HTTP Message Signatures (RFC 9421)HTTP Message Signatures is an IETF standard, published as RFC 9421 in February 2024, for creating and checking digital signatures over selected parts of an HTTP message, such as the method, host and certain headers. It defines the Signature-Input and Signature headers. Web Bot Auth uses it so bots and AI agents can sign their requests.
  • Identity linkingIdentity linking is a capability of the Universal Commerce Protocol (UCP) that lets an AI agent or shopping platform act on a shopper's existing account at a store, after the shopper signs in and approves it through OAuth 2.0. The agent gets a token limited to the permissions the shopper approved, and never receives the shopper's password.
  • Instant Checkout (ChatGPT)Instant Checkout was a ChatGPT feature, launched on September 29, 2025, that let US users buy from some merchants without leaving the chat. It ran on the Agentic Commerce Protocol (ACP), with payments powered by Stripe. In March 2026 an OpenAI spokesperson, quoted by Digital Commerce 360, said Instant Checkout was moving to apps.
  • Intent MandateAn Intent Mandate is a signed record, in Google's original design of the Agent Payments Protocol (AP2), of what a person asked an AI agent to do, such as which item to look for, plus the conditions they set, such as price limits and timing. The current AP2 documentation no longer uses the name and describes the same step as the open stage of its Checkout and Payment Mandates.
  • Intermediary agentAn intermediary agent is an AI agent service that many different end users operate, where the company runs the software but each action is started by a user. Cloudflare uses Intermediary as a label on Verified bots from July 1, 2026, in contrast to Direct bots, which a single, narrow operator runs.
  • Know Your Agent (KYA)Know Your Agent (KYA) is the practice of confirming an AI agent's identity, the person or business it acts for, and what it is allowed to do, before trusting it with access or a payment. The term is used by several payment companies and protocol authors, and there is no single KYA standard yet.
  • llms.txtllms.txt is a proposed Markdown file, usually served at /llms.txt on a website. It gives large language models and AI tools a short summary of the site and a curated list of links to its most useful pages. Jeremy Howard proposed it in September 2024. It is a community proposal, not a formal standard, and Google says Google Search does not use it.
  • Machine Payments Protocol (MPP)The Machine Payments Protocol (MPP) is an open standard for machine-to-machine payments over HTTP. When an agent asks for a paid resource, the server answers with HTTP 402 and payment details, the agent authorizes a payment and retries, and the server returns the resource with a receipt. Stripe and Tempo co-authored it and announced it in March 2026.
  • Merchant of recordThe merchant of record is the business legally responsible for selling to the customer and processing their payment, including sales tax, refunds and chargebacks. In agent checkout standards such as UCP and ACP, and in Microsoft's Copilot Checkout, the store remains the merchant of record even when the order is placed through an AI assistant.
  • Model Context Protocol (MCP)The Model Context Protocol (MCP) is an open-source standard for connecting AI applications to external systems. An MCP server offers tools and data, and an AI app such as Claude or ChatGPT connects to it as a client to look things up or take actions. Anthropic contributed it to the Linux Foundation's Agentic AI Foundation in December 2025.
  • Personal Agent Protocol (PAP)The Personal Agent Protocol (PAP), also called Poppy, is an open standard for how a person's own AI agent works with a business on their behalf: how it finds the business, identifies itself and the person it acts for, and gets access as a guest or signed in. It is being developed by Meta and Sierra, and version 1.0 was published in November 2026. It carries no payment itself.
  • Prompt injectionPrompt injection is when input to an AI model, often instructions hidden in a web page, email or document the model reads, changes its behavior in ways its user did not intend. For AI agents that browse and act on websites, it can mean an attempt to make the agent take actions its user never asked for. OWASP lists it first in its 2025 Top 10 risks for LLM applications.
  • Reverse DNS verificationReverse DNS verification is a check that a visitor claiming to be a known bot really comes from that bot's operator. You look up the hostname for the request's IP address, confirm it ends in the operator's domain, then look up that hostname and confirm it points back to the same IP address.
  • robots.txtrobots.txt is a plain text file at the top level of a website that lists which URLs automated crawlers may and may not fetch. It follows the Robots Exclusion Protocol, standardized as RFC 9309 in September 2022. It is a request that well-behaved crawlers honor. It does not block anyone and it does not control login or access.
  • Shared Payment Token (SPT)A Shared Payment Token (SPT) is a Stripe credential that an AI agent grants to a seller so the seller can charge a customer's payment method for an agent-initiated purchase. Each token carries limits set by the agent, such as currency, maximum amount and expiry, and stops working once it is used up, expires or is revoked.
  • Signature-Agent headerSignature-Agent is an HTTP request header used in Web Bot Auth. It carries an https URL that points to where a bot or AI agent publishes its public signing keys, so a website can fetch them and check the request's signature. ChatGPT, for example, sends the value "https://chatgpt.com" on its signed requests.
  • Signed agentA signed agent is an AI agent whose web requests carry a cryptographic signature, usually through Web Bot Auth, so a website can confirm which service sent them. Cloudflare introduced "signed agents" as a bot category in August 2025 and, from July 1, 2026, folded it into Verified bots with a Direct or Intermediary label.
  • Training crawlerA training crawler is a bot that visits websites to collect content that may be used to train or fine-tune AI models. Examples include OpenAI's GPTBot and Anthropic's ClaudeBot. Operators publish a separate robots.txt token for training, so you can block it without blocking their search or user-triggered bots.
  • Trusted Agent Protocol (TAP)Trusted Agent Protocol (TAP) is a framework from Visa, announced on October 14, 2025 and developed with Cloudflare, that lets merchants recognize registered AI shopping agents. Agents sign their requests using HTTP Message Signatures and can pass details about the shopper and payment, which the merchant checks against keys Visa publishes.
  • Universal Commerce Protocol (UCP)The Universal Commerce Protocol (UCP) is an open-source standard that lets AI agents and apps shop with a business: search its catalog, build a cart, link a shopper's account, check out and manage the order. Google developed it with retailers and platforms including Shopify, and the business stays the merchant of record.
  • User agentA user agent is the software making a web request, and the User-Agent is the HTTP header where it names itself. The string can include the app, its version, the operating system and the vendor. Any client can send any value, so it is a claim, not proof.
  • User-triggered fetcherA user-triggered fetcher is an automated client that loads a web page because a person asked a product to, not as part of a crawl. Examples include ChatGPT-User, Perplexity-User and Google-Agent. Because a person requested the visit, operators such as Google and Perplexity say these fetchers generally ignore robots.txt rules.
  • Verifiable IntentVerifiable Intent is an open specification for cryptographic proof that an AI agent's actions stayed within the scope a person delegated to it. It links credentials from the card issuer, the user and the agent in a tamper-evident chain. Mastercard maintains it, co-developed it with Google to work with AP2, and contributed it to the FIDO Alliance in April 2026.
  • Verified botA verified bot is an automated visitor whose claimed identity has been checked and confirmed. Checks include reverse DNS lookups, matching against IP ranges the operator publishes, or a cryptographic signature on the request. A name in the User-Agent header alone is not verification.
  • Web Bot AuthWeb Bot Auth is a way for bots and AI agents to prove who they are by cryptographically signing each HTTP request, using HTTP Message Signatures (RFC 9421). The operator publishes its public keys, and a website or its firewall checks the signature against them. It is being standardized in an IETF working group and is not yet an RFC.
  • x402x402 is an open protocol for paying over HTTP. A server answers a request for a paid resource with status 402 Payment Required and the payment details, the client pays and retries the request with proof of payment, and the server returns the resource. Stripe's implementation, for example, settles payments in the USDC stablecoin.

See which AI agents visit your site, and decide what they may do.

Scan your site free