Explain a term

The agentic economy, in plain English.

The protocols agents use to reach businesses and pay, and the disciplines that claim to measure or improve how agents treat a brand. What each one is, what it is not, and who provides it.

Protocols

Different protocols govern different handoffs. A specification is not proof of deployment: a working connection still depends on authorization, versions, region and onboarding.

MCP

Agent ↔ tool/data
Established · Linux Foundation AAIFSpecification

The standard way an AI agent plugs into tools and data: a calendar, a CRM, a company's own systems. Created by Anthropic; now stewarded by the Linux Foundation's Agentic AI Foundation.

Key distinction: Connect to tools, services and data; not a peer-agent collaboration protocol.

not A2A · agent ↔ agentnot Poppy · personal agent ↔ businessnot UCP · checkout

Full record · 18 relationships →Specification ↗

A2A

Agent ↔ agent
Open protocol / implementationSpecification

A way for one AI agent to find another, hand it a task and get the work back.

Key distinction: Discover other agents, delegate tasks, exchange work.

not MCP · agent ↔ toolsnot Poppy · personal agent ↔ business

Full record · 9 relationships →Specification ↗

Poppy — Personal Agent Protocol

Personal agent ↔ business
Draft v0.1 · published 9 Oct 2026Specification

A draft protocol for a customer's personal agent to identify itself to a business, get the customer's consent and open a session.

Key distinction: Identity, business discovery, sessions, consent, cross-channel access.

not MCP · agent ↔ toolsnot UCP · checkoutnot A payment rail

Full record · 45 relationships →Specification ↗

UCP — Universal Commerce Protocol

Shopping agent ↔ merchant
Open standard · UCP Tech CouncilSpecification

An open specification for shopping agents to work with merchants, from browsing a catalog through checkout and order tracking.

Key distinction: Commerce activities including checkout and order lifecycle.

not ACP · ChatGPT checkoutnot AP2 · payment authority

Full record · 8 relationships →Specification ↗

Agentic Commerce Protocol (ACP)

AI commerce ↔ merchant
Open protocol (OpenAI + Stripe)Specification

The Agentic Commerce Protocol from OpenAI and Stripe: how merchants expose product feeds and checkout to AI agents. It powered ChatGPT Instant Checkout until March 2026; it is now used for product feeds and by Microsoft Copilot Checkout.

Key distinction: Merchant product feeds and agent checkout. Not IBM's Agent Communication Protocol (now part of A2A).

not UCP · Google and Shopify's commerce standardnot AP2 · payment authoritynot IBM's Agent Communication Protocol (now part of A2A)

Full record · 6 relationships →Specification ↗

AP2 — Agent Payments Protocol

Agent ↔ payment authority
v0.2 · Google → FIDO Alliance (Apr 2026)Specification

A protocol for proving that a customer authorized an agent to make a specific purchase, using signed mandates. Created by Google; stewarded by the FIDO Alliance since April 2026.

Key distinction: Proof of purchasing intent, signed mandates and payment records.

not UCP or ACP · the checkout itselfnot A card network

Full record · 5 relationships →Specification ↗

OAuth / OIDC

User ↔ service permission
Mature identity standardsSpecification

Delegated user authentication/authorization used by systems including Poppy.

Full record · 2 relationships →Specification ↗

OpenAPI

Developer ↔ API
Mature specificationSpecification

Machine-readable descriptions of APIs, not an agent execution layer.

Full record →Specification ↗

x402

Agent ↔ API / content (payment)
Open protocol · x402 FoundationSpecification

An open protocol for agents to pay for APIs and content per request, using the web's HTTP 402 'payment required' code.

Key distinction: Pays per request over HTTP 402. Not a checkout protocol like ACP or UCP.

not ACP or UCP · shop checkoutnot AP2 · proving authority to pay

Full record · 2 relationships →Specification ↗

ACORD data standards (GRLC, P&C)

Insurer ↔ broker ↔ reinsurer (data)
Published · ACORDSpecification

Defines insurance messages and data. Agents can use it, but it is not an agent protocol.

Full record · 1 relationships →Specification ↗

Core Data Record (CDR)

London market placement and claims (data)
Published · London Market GroupSpecification

A market data standard, not a personal-agent protocol.

Full record →Specification ↗

Agent Mediated Insurance (AMI)

Customer agent ↔ insurer (quote, compare, bind)
Working draft · MarrowSpecification

Insurance-specific consent, disclosure and audit rules for agent buying. Not a universally supported standard.

Full record · 1 relationships →Specification ↗

Proposed technical report · CEN (comment to 14 Nov 2026)Specification

Guidance on mapping insurance data to MCP tools. A proposal, not a standard.

Full record →Specification ↗

Other standards and extensions

Agentic Checkout SpecSpecification Published specification

OpenAI's checkout specification within the Agentic Commerce Protocol (ACP): how an agent completes a purchase with a merchant on the user's behalf.

Agent-to-UI (A2UI)Specification Published specification

A2UI is an open protocol that lets AI agents send interface layouts as declarative JSON, which client apps render natively on web, mobile and desktop.

Agent–User Interaction Protocol (AG-UI)Specification Published specification

An open protocol for how an AI agent streams its actions and results into an application's user interface.

HTTPSpecification Published specification

RFC 9110 (HTTP Semantics, IETF Internet Standard) defines the architecture, terminology and semantics shared by all HTTP versions.

An open protocol that lets software agents pay for APIs and services over HTTP, using the 402 'payment required' response.

MCP Apps extensionSpecification Published specification

An official MCP extension that lets tools return interactive interfaces, such as forms, charts and dashboards, shown inside the chat; supported by ChatGPT, Claude, Goose and VS Code.

OpenID Connect for agentsCandidate / unreviewed

OpenID Foundation work, led by its AI Identity Management Community Group, on how AI agents prove identity and act for users, building on OpenID Connect and OAuth.

Measurement and visibility disciplines

Each works on different phases of a buying decision. One question separates them: does it tell you who wins? See them side by side in the buying journeys.

SEO

Search engine optimization

Improves how a company's pages rank in web search, one of the sources agents draw on during discovery.

Tells you who wins? No Gets you found, strongly on Google's AI Overviews, weakly elsewhere. Doesn't tell you whether you win.

Ahrefs (Aug 2025, 15,000 prompts): Only about 8% of the pages ChatGPT, Gemini and Copilot cite rank in Google's top 10. Source ↗

Show all the evidence (7)

Semrush (Jul 2026, 50,000 brands): SEO metrics predicted which brand ChatGPT names for a topic only about half the time. Source ↗

University of Toronto (Jan 2026, preprint): 4–15% overlap between Google results and the sources AI assistants cite. Source ↗

Peer-reviewed GEO study (KDD 2024): Content changes lifted a fifth-ranked site's AI visibility by 115%; Google rank doesn't lock it in. Source ↗

Counter-finding: Seer Interactive (Jan 2025): Page-one Google rank was the strongest predictor of brand mentions in GPT-4o, with a correlation of about 0.65 (single questions, mentions only). Source ↗

Google AI Overviews: Track rankings more closely: 38–76% of their citations come from the top 10 (Ahrefs, BrightEdge, seoClarity). Source ↗

The final recommendation: No published study links SEO to the brand an assistant finally recommends. AIVO's research is the only work on this so far (internal, Oct 2026, publication planned).

SEO agencies and tools. Not yet cataloged in the Atlas: submissions welcome.

AI visibility (GEO)

First-prompt mentions and citations

Tracks and improves how often a brand is mentioned or cited in an assistant's first answer.

Tells you who wins? No Gets you into the conversation. Doesn't decide who wins.

AIVO published research: 87.3% of brands named at the first turn of a buying conversation were displaced by a competitor by the fourth turn (n=1,427 brand probes, 10 industries). Source ↗

Visibility, GEO and SEO tools are outside the Atlas's scope: they measure being seen, not being chosen.

Agent access & content readiness

Feeds, structured data, agent access points

Makes a company's information easy for agents to retrieve and understand.

Tells you who wins? Partly Makes your facts available. Available is not the same as used.

AIVO published research: 75.7% of the facts models held about a brand were not used when they made a recommendation (n=592 facts, 22 brand-SKUs). This is the Linkage Gap. Source ↗

Providers that meet the published criteria for agent access and content readiness will be listed here.

Evidence for agents

Facts and proof agents can use · e.g. brand.context

A machine-readable file, published on a brand's own website, that gives agents the brand's facts with the evidence behind them. AIVO's remedy for the Linkage Gap.

Tells you who wins? Designed to Designed to carry a brand's facts and evidence through to the decision.

Vendor documented (AIVO): Published as an AIVO specification. Classified like any vendor capability.

Agent journey tracking

Turn-by-turn

Follows realistic multi-turn conversations to see where a brand enters the shortlist and where it falls out, and why.

Tells you who wins? Partly Shows where, turn by turn, a brand is dropped.

Vendor documented (AIVO): Measured in controlled multi-turn buying conversations; diagnoses include the Linkage Gap and Evidence Gap.

AI Win Rate · decision research

Who is chosen, and who wins instead

Runs realistic buying conversations and records how each ends: an outright pick, a shared shortlist, a referral elsewhere, or no pick. Win rate is the share won outright; shared listings are reported separately.

Tells you who wins? Yes Measures the final choice directly.

Published methodology (AIVO): AI Win-Rate Methodology v2.0: how outright final recommendations are counted, with shared listings, referrals and no-picks reported separately. Source ↗

Show all the evidence (2)

Vendor documented (AIVO): Controlled research outcomes, not observed sales.

AI traffic attribution

Visits and sales that came from AI

Attributes website visits and sales to the AI assistants and agents that referred them, so a business can see what arrived through AI.

Tells you who wins? Partly Shows what AI sent you, after the fact. Not who was chosen instead.

Draft convention (AIVO): ATAC, the AI Traffic Attribution Convention: v0.1 draft for public comment, July 2026. Source ↗

ATAC is an open draft convention published by AIVO. Analytics and attribution vendors are not yet cataloged in the Atlas: submissions welcome.

Providers shown are those included under the published criteria, listed alphabetically. No paid placement. Know a provider with published evidence? Suggest one →

AIVO measures

Terms used in the AIVO Meridian row of the buying journeys. AIVO, Inc. publishes this Atlas; these are its own measures, explained plainly.

Legibility

AIVO Meridian

Whether AI agents can read what a business offers and put it on the lists it belongs on, alongside its real competitors. A brand can be well known to an assistant and still not surface: that is a legibility gap, not an awareness gap.

AIVO research: The Product Data Legibility Gap ↗

Linkage Gap

AIVO Meridian

Facts a business publishes that agents hold but never use when they make the final recommendation. Closed by publishing evidence in a form agents use at the decision, such as brand.context.

AIVO research: Beyond Visibility, the Linkage Gap ↗

Displacement

AIVO Meridian

The turn in a multi-turn conversation at which a brand drops out of the agent's shortlist, who replaces it, and why. Remediation targets that turn.

AIVO explainer: Found is not recommended ↗

AIRQ (AI Reputation Quotient)

AIVO Meridian

How AI assistants describe a company across six dimensions (trust, vision, products and services, relevance, ethics, culture) through five lenses (consumer, employee, investor, regulator, impact of AI), against a fixed set of peers.

Method: AIVO Methodology v4.1 ↗

Revenue at Risk (RaR-AID)

AIVO Meridian

An estimate of the revenue exposed when AI agents recommend someone else: category revenue, multiplied by the share of purchases AI influences, multiplied by the measured rate at which agents displace the brand.

Published method: RaR-AID working paper ↗AIVO explainer: What it's costing you ↗

Poppy design participants · 44

Sierra and Meta, plus 7 launch partners (6 Oct 2026) and 35 design partners (9 Oct 2026). Membership does not establish that a participant's products use Poppy.