Skip to content

Latest commit

 

History

1 Commit

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 

Repository files navigation

The Agentic Advertising Stack

A curated map of the protocols, standards, and infrastructure that let AI agents plan, buy, sell, deliver, and measure advertising. Organized by layer, from the generic agent protocols at the bottom up through ad-specific protocols, sell-side and buy-side infrastructure, commerce, identity, and the publisher/content signals that decide what AI surfaces are allowed to monetize.

This list covers the infrastructure and standards layer. For MCP servers and tools that drive individual ad platforms (Google, Meta, TikTok, LinkedIn and so on), see awesome-agentic-advertising, which does that well and which this list does not try to duplicate.

Disclosure. I am a co-founder of Adgentek, so read the Adgentek entries accordingly; each is marked (disclosure: my company). Adgentek is a Founding Member of AdCP and a member of IAB and IAB Tech Lab. My aim is to cover every serious effort in the space on equal footing regardless of governing body.

Last updated: September 5, 2026. Pull requests welcome; see Contributing.

Contents

  1. Foundation protocols
  2. Advertising protocols and standards bodies
  3. Sell side: sales agents, ad servers, and adapters
  4. Buy side: buying agents and orchestrators
  5. First-party MCP servers from major ad platforms
  6. Registries, discovery, and adoption tracking
  7. Agent identity and trust
  8. Agentic commerce and payments
  9. Publisher content, licensing, and AI-surface monetization
  10. Measurement and attribution
  11. Creative and provenance
  12. Reading
  13. Related lists

1. Foundation protocols

The general-purpose agent protocols everything above them is built on.

  • Model Context Protocol (MCP) - Agent-to-tool protocol originated by Anthropic, now under the Linux Foundation's Agentic AI Foundation. AdCP and AAMP both run over it. Docs.
  • Agent2Agent (A2A) - Agent-to-agent communication and task delegation, originated by Google, now Linux Foundation governed. AdCP supports it as a second transport.
  • WebMCP - Browser-native variant that lets web pages expose tools directly to agents. Relevant to on-page ad experiences agents interact with.
  • Agent Skills - Specification for packaging reusable agent capabilities. The likely container for "ad buying as a skill" any agent can load.
  • AGENTS.md - Open format for guiding coding agents inside a repo; increasingly used as a general agent-instructions convention.
  • Agent Network Protocol (ANP) - Decentralized agent discovery and communication built on W3C DIDs. Early, but the DID approach is relevant to agent identity below.
  • Agentic AI Foundation (AAIF) - The Linux Foundation home for MCP, A2A, AP2, UCP and related work, including an Agentic Commerce Working Group.

2. Advertising protocols and standards bodies

The ad-specific protocols and the organizations that govern them.

AdCP (Ad Context Protocol), AgenticAdvertising.org

Open protocol for agents to discover, plan, buy, sell, and measure media. Published and governed by AgenticAdvertising.org (AAO). Current spec is 3.1, with a 3.2 preview available on the AAO site. Launched publicly October 15, 2025 with Yahoo, PubMatic, Optable, Scope3, Swivel and Triton Digital as founding members and 20-plus supporting companies.

AAMP (Agentic Advertising Management Protocols), IAB Tech Lab

IAB Tech Lab's umbrella initiative for agentic advertising, formally published March 16, 2026 across three pillars: Agentic Foundations, Agentic Protocols, and Trust and Transparency. AAMP 2.3 shipped July 30, 2026. Tech Lab has said it will "agentify" its existing standards (OpenRTB, ads.txt, sellers.json, VAST and others) under this umbrella and ship Agentic Protocol SDKs.

Other

  • Prebid Sales Agent - Prebid.org's media sales agent implementing the AdCP Media Buy protocol. The main open-source sell-side agent today.

3. Sell side: sales agents, ad servers, and adapters

Infrastructure that lets a publisher, AI surface, or SSP expose inventory to buying agents.

  • Prebid Sales Agent - Open-source AdCP sales agent from Prebid.org. Multi-tenant, with adapters to downstream ad servers.
  • IAB Tech Lab seller agent - AAMP reference seller.
  • Adgentek Agentic Ad Server and AdsMCP (disclosure: my company) - Ad server built for AI surfaces (chat assistants, answer engines, agents). AdsMCP is the MCP integration path into it, letting an AI surface or agent request and render ads over MCP. Repo.
  • Scope3 Storefronts - Sell-side listings on Scope3's Interchange, discoverable to any buying agent that speaks AdCP.
  • AdCP reference creative agent - Creative generation and adaptation as a sell-side or third-party service in the AdCP flow.

4. Buy side: buying agents and orchestrators

Agents that translate a brief, budget, and guardrails into media decisions and transact with sell-side agents.

  • IAB Tech Lab buyer agent - AAMP reference buyer.
  • Adgentek ORCA (disclosure: my company) - Orchestrated Real-time Collaborative Agents. Buy-side platform that sits above the transaction layer and dispatches outcome agents to AdCP-compliant sell-side infrastructure. Not a DSP. Background: The Two Paths of Agentic Media Buying.
  • Scope3 Interchange - Agent-to-agent marketplace built on AdCP where buying agents discover, negotiate, and transact with sales, signals, creative, and governance agents. Connects into Claude and ChatGPT as a connector; plugin repo and TypeScript client.
  • Guidance for Advertising Agents on AWS - Amazon's sample multi-agent advertising stack on Bedrock AgentCore, including an AdCP MCP gateway.
  • Kochava StationOne - Desktop orchestration layer connecting AI models and ad tech tools through API keys and MCP; its AAMP workspace was open-sourced with IAB Tech Lab in March 2026.

5. First-party MCP servers from major ad platforms

One inclusion rule: the MCP server is operated by a major ad platform (a walled garden or social/retail platform selling its own inventory) and gives third-party agents access to that platform's ad stack. This is the "walled gardens opening up" signal, and it is the one thing the registries do not capture. DSPs, SSPs, and other ad tech vendors belong in the registries in the next section, whether or not they ship an MCP server; community wrappers and marketing-tool connectors belong in awesome-agentic-advertising.

  • Amazon Ads MCP Server - Open beta announced at IAB ALM, February 2, 2026. Amazon-hosted; bundles multi-step workflows (campaign launch, locale expansion, reporting) into tools. Full create, update, and delete.
  • Google Ads MCP - Google's official open-source MCP server for the Google Ads API, released October 2025. Read-only diagnostics and GAQL queries.
  • Meta Ads MCP Server - Meta Ads AI Connectors, launched April 29, 2026, at mcp.facebook.com/ads. Performance reporting, campaign and catalog management, and signal diagnostics; per-app Read or Manage scope, with writes landing paused. Meta MCP overview.
  • Microsoft Advertising MCP Server - First-party server launched June 17, 2026 as an open pilot. Read-only campaign data inside Copilot, Claude, and other assistants.
  • Pinterest MCP - Announced June 17, 2026 in alpha with agency partners including PMG, Pacvue, and Dentsu; read-only. No public developer docs yet; see PPC Land.
  • Snapchat Ads MCP Server - Snap-hosted server at mcp.snapchat.com/ads, launched August 3, 2026, supporting Claude, ChatGPT, Codex, and Gemini. Read-only at launch; Organization Admins authorize each agent separately, with write access to follow as a per-agent grant. Announcement.
  • TikTok for Business MCP Server - TikTok's official MCP bridge for connecting AI agents to the TikTok Ads platform, including campaign creation and bid adjustments.
  • X Ads MCP - Official remote MCP server built into X's Ads API gateway at ads-api.x.com/mcp. 23 tools spanning reads, analytics, targeting search, and writes; the user's own OAuth2 token scopes access, and every campaign or line item is created paused.

6. Registries, discovery, and adoption tracking

How agents find each other, prove who is authorized to sell what, and how the ecosystem tracks who is actually live.

7. Agent identity and trust

The thin layer between "a legitimate buying agent" and "invalid traffic." Mostly borrowed from the commerce and bot-management worlds so far; ad-specific attestation is still open ground.

  • Web Bot Auth - Cloudflare-led IETF drafts (built on RFC 9421 HTTP Message Signatures) for agents to cryptographically sign requests so the receiving side can verify identity. Still an individual Internet-Draft as of August 2026, but verified in production by Cloudflare and adopted by major agent operators. Cloudflare docs.
  • Visa Trusted Agent Protocol (TAP) - Visa's agent-to-merchant trust framework using HTTP Message Signatures (RFC 9421), built on Web Bot Auth. Announced October 2025.
  • Mastercard Agent Pay / Verifiable Intent - Agentic Tokens extending MDES so verified agents can transact on a consumer's behalf; the Verifiable Intent framework was contributed to the FIDO Alliance alongside AP2 in April 2026. See the AAIF explainer.
  • Agent Payments Protocol (AP2) - Signed Intent, Cart, and Payment mandates (W3C Verifiable Credentials) proving what a user authorized an agent to do. Google contributed AP2 to the FIDO Alliance in April 2026.
  • Agent Network Protocol (ANP) - DID-based agent identity, listed again here for the identity angle.

8. Agentic commerce and payments

Where the ad converts. When the agent that saw the ad is the agent that checks out, outcome measurement runs through these protocols rather than pixels.

9. Publisher content, licensing, and AI-surface monetization

The standards deciding whether AI surfaces pay for the content they use, monetize it with ads, or both.

  • Really Simple Licensing (RSL) - Machine-readable licensing terms in robots.txt and feeds: free, attribution, subscription, pay-per-crawl, pay-per-inference. Launched September 10, 2025 with Reddit, Yahoo, People Inc., Medium and others. Repo.
  • Content Monetization Protocols (CoMP) - IAB Tech Lab protocol for establishing commercial terms between publishers and AI systems before content is accessed. Version 1.0 released for public comment March 23, 2026.
  • Cloudflare Content Signals - robots.txt directive (ai-train, ai-input, search) declaring what AI may do with content. Submitted to the IETF AIPREF working group.
  • Cloudflare Pay Per Crawl - HTTP 402 based charging for crawler access, gated on Web Bot Auth.
  • llms.txt - Convention for telling language models how to use a site.
  • NLWeb - Microsoft's reference implementation for natural-language interfaces to websites, exposed over MCP.
  • SPUR Telemetry - Emerging standard for measuring how publisher content is used inside AI systems. See the INMA overview.

10. Measurement and attribution

The open problem. Clicks, UTMs, and referrers do not survive an AI intermediary, and nobody yet agrees who gets credit when an agent reads, compares, and buys.

  • IAB AI advertising measurement framework - In development by IAB (the trade group, distinct from Tech Lab) with a working group of platforms, publishers, agencies, measurement vendors, and brands; scheduled for release November 12, 2026. Aims to separate AI's awareness-level influence from its role in the actual decision.
  • AAO Registry measurement agents - The AdCP registry crawls measurement agents' capabilities and exposes them as a queryable metric catalog (attention, viewability, MRC accreditation filters).
  • IAB Tech Lab measurement standards being agentified - OMID / OM SDK for exposure events and ECAPI for outcome events are on Tech Lab's list of standards to extend for agents under AAMP.
  • SPUR Telemetry - Measurement of how publisher content is used inside AI systems; see the publisher section above.

11. Creative and provenance

12. Reading

Explainers and reporting worth the time, most recent first.

13. Related lists


Contributing

Open a pull request. One entry per line, in the form [Name](url) - one sentence on what it is and why it matters. Entries need a live, public artifact: a spec, a repo, an API, or a shipping product. Announcements without an artifact go in Reading. If you are adding your own company, say so inline the way the Adgentek entries do.

License

CC0 1.0 Universal. Copy, fork, and reuse freely.

About

A curated map of the agentic advertising stack - protocols, standards, sell-side and buy-side infrastructure, commerce, identity, and publisher/content signals. AdCP, AAMP, MCP, A2A, UCP, AP2, Web Bot Auth, RSL/CoMP and more.

Topics

Resources

Stars

4 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors