Every decade or so, a technical standard emerges that quietly rewires who holds power in advertising. OpenRTB did it in 2010. The TCF did it for consent. Now, two competing frameworks for agentic AI advertising are fighting for the same prize — and the outcome will shape whether the open web gets more open or less.
The Contenders
The Ad Context Protocol (AdCP) is a ground-up open-source framework built on Anthropic's Model Context Protocol. It proposes a world where AI agents autonomously discover inventory, negotiate deals, and execute campaigns — talking directly to publishers without the usual cast of intermediaries. Its core concept is the DEAL: a structured, machine-readable agreement between a buyer agent and a seller that maps cleanly to how a marketplace or direct publisher relationship already works.
The IAB Tech Lab's AAMP (and its sub-components ARTF and UCP) takes a different approach: layer AI orchestration on top of the existing OpenRTB infrastructure rather than replace it. The pragmatic argument is that OpenRTB already works at scale, is already broadly compliant, and is already implemented by thousands of platforms.
These two frameworks are not direct apples-to-apples alternatives. AdCP is primarily about the deal-making layer — how agents discover inventory and agree terms. AAMP is more tightly coupled to the real-time auction and serving infrastructure. Understanding that distinction matters for what follows.
The Problem with AAMP
AAMP's approach routes deal-making through existing SSPs and DSPs. That means neither the publisher nor the advertiser gets full visibility into what the other is seeing — the same structural opacity that has eroded publisher yields for a decade. Building AI agents on top of that architecture may make the system faster and smarter, but it does not change what it fundamentally does.
AdCP's DEAL concept, by contrast, is designed for direct, transparent negotiation between buyer and seller agents. That maps naturally to a marketplace model where both sides can see what they are agreeing to.
The EU Variable Nobody Should Be Treating as a Footnote
Any agentic protocol that processes user data must handle consent signals compliantly in European markets. That is not optional. AdCP's current specification does not provide a clear, auditable mechanism for TCF consent signal passing. The IAB Tech Lab's approach at least starts from a framework with existing consent architecture — though UCP's handling of user context data will require careful scrutiny as the specification matures.
European publishers and vendors cannot run experiments with consent compliance. We will continue to push for GDPR and TCF compatibility as a first-class requirement in both specifications, not a retrofit.
The Bigger Picture: An Existential Threat to Publishers
There is a dimension to this debate that deserves more attention than it typically receives. AI agents are already taking traffic away from publishers — users increasingly get answers without clicking through — and products like OpenAI's ads.openai.com represent an attempt to sell that traffic back to advertisers directly, cutting publishers out entirely. It is the Facebook playbook, version 2.0, and for smaller publishers it is an existential threat.
Agentic advertising protocols are one of the more credible structural responses to that threat. If buyers can reach publishers directly through an open protocol — discovering inventory, negotiating deals, and transacting transparently — then the middleman that extracts margin while providing opacity loses its grip. Getting these protocols right is not a technical niche concern. It is strategically important for the future of independent publishing.
For us at Adnuntius, the subtext is direct: if we do not get involved in shaping and implementing these protocols now, our marketplace could over time be displaced by them. That is not a reason to resist — it is a reason to move quickly and build something genuinely better.
What This Means for Publishers and Independent Vendors
Both AdCP and AAMP share a practical challenge: in their standard form, they require both publishers and advertisers to download, install, and configure agent software so their systems can talk to each other and negotiate a DEAL. For a large platform with engineering resources, that is manageable. For a mid-sized independent publisher, it is a real barrier.
After careful evaluation, we have made our choice: we are building on AdCP. And we are doing it in a way that removes that barrier entirely.
Our Answer to the Scaling Challenge
Adnuntius operates as both an SSP and a DSP — in practice, a single unified system serving both publishers and buyers through our marketplace. This gives us a specific structural advantage in the agentic era.
We are building an MCP server that both sides can connect to instead of installing agent software themselves. A buyer's agent connects to our MCP server and interacts with our marketplace; a publisher's inventory is represented through that same server. Neither side needs to implement AdCP independently. The marketplace acts as the AdCP-compatible layer, and the DEAL that AdCP specifies maps directly to how our marketplace already allocates inventory — with full transparency to both sides, and without an SSP or DSP extracting margin in between.
This also addresses the reach problem that makes AdCP risky for individual publishers. A buyer making a single request through our MCP server gets responses from across our entire publisher network. Smaller and independent publishers participate through the marketplace without needing to build anything new — and they retain the transparency and control that makes AdCP worth using in the first place.
Our Position
We are committed to AdCP and are building the infrastructure to make it work for publishers who cannot wait for a standards war to resolve. We believe the marketplace model has genuine advantages that neither protocol alone can replicate: better and faster inventory allocation across publishers, a single integration point for both sides, and a compliance layer that handles GDPR and TCF requirements from day one rather than as an afterthought.
We remain engaged with the IAB Tech Lab's process — not to hedge, but because the consent and interoperability questions both frameworks must answer are best resolved through industry dialogue rather than in isolation.
The agentic era of advertising is coming whether the industry is ready for it or not. Our bet is that it should arrive as a genuinely better system — one where independent publishers have more control, not less, and where transparency is structural rather than aspirational. We are building accordingly, and we are building now.