The agentic advertising market is splitting in two, and almost everyone is focused on the same layer.
Layer 1 is campaign management agents. These are AI systems that help human advertisers run campaigns on existing platforms. Amazon's MCP Server lets you manage Amazon Ads through Claude or ChatGPT. Meta embedded Manus AI into Ads Manager. Walmart's Marty agent handles ad workflows for suppliers. Dstillery's DS-1 executes programmatic buys on The Trade Desk through a Slack-based MCP integration.
Layer 1 is well-funded and shipping fast. Amazon's MCP Server entered open beta in February. The Dstillery-Keynes-Trade Desk partnership went live in March. NBCUniversal completed the first AI-agent-led programmatic guaranteed deal during the NFL playoffs.
Layer 2 is different. Layer 2 is ad delivery inside AI tool interactions. Not an agent managing a Google Ads dashboard, but an MCP server returning a sponsored result alongside organic results when a user asks "what CI/CD tool should I use?"
Layer 1 automates the advertiser's workflow. Layer 2 creates a new ad surface where none existed before.
Why Layer 1 Gets All the Attention
It's obvious. Layer 1 takes an existing multi-billion dollar market (programmatic advertising) and makes it faster. The value proposition is clear: reduce campaign setup time by 87% (PubMatic's reported number with Claude). Cut media buying from 48 hours to 5 minutes (Dstillery's claim).
Every ad tech company understands this pitch. It fits neatly into existing budgets, existing metrics, existing org charts. The CFO doesn't need a new line item. The media buyer doesn't need a new skill. They just do what they already do, but faster.
Layer 1 also has obvious buyers. Amazon Ads has millions of advertisers who would pay for better campaign automation. Meta has the same. The TAM is calculable and large.
Why Layer 2 Matters More Long-Term
Layer 1 makes existing advertising more efficient. Layer 2 creates advertising inventory that didn't exist before.
Consider what happens when MCP adoption scales to its projected trajectory. The ecosystem already has 11,000+ servers, 97 million monthly SDK downloads, and 85% month-over-month growth. When millions of tool calls happen daily across thousands of MCP servers, each one represents a micro-decision: which database, which API, which hosting provider, which framework.
Today, those recommendations happen with zero commercial layer. The MCP server that recommends PlanetScale over Neon is delivering qualified intent to PlanetScale for free. In a browser, that same recommendation would be a paid referral link on a blog post.
Layer 2 is the programmatic referral link for AI tool interactions. It turns unpaid tool recommendations into a marketplace.
The Current Layer 2 Landscape
Almost nobody is building here yet. The companies I can find:
agentic-ads (us) - open-source MCP ad network. Publishers add search_ads() to tool handlers, get 70% revenue in USDC on Base. 270 tests, live on Railway, E2E validated.
AdCP's Signals Activation Protocol - could theoretically support tool-level ad delivery, but it's designed for traditional media buying workflows between SSPs and DSPs. The spec is at v3.0.0-rc.1 and focused on programmatic guaranteed and PMP deals, not single-tool-call micropayments.
MonetizedMCP - open-source framework for USDC payments on MCP servers, but it's payment infrastructure (pay-per-use), not advertising. Complementary, not competing.
MCPize / Apify - marketplaces for paid MCP tools. Pay-per-event model. Again, payment infrastructure rather than ad-supported free tools.
There's a meaningful gap between "charge users per call" (MCPize model) and "keep tools free, monetize through contextual ads" (Layer 2 model). Both can coexist. Most consumer internet works this way: some services charge directly, others are ad-supported.
The Standards Question
Two competing standards efforts are shaping how this space develops:
AdCP (Ad Context Protocol) - built on MCP by AgenticAdvertising.org. Founding members include Yahoo, PubMatic, Magnite, Media.net. Four modules: Signals Activation, Media Buy, Creative, and Curation (Q2 2026). Founding membership open through March 31, 2026.
IAB Tech Lab - extending existing standards (OpenRTB, AdCOM, VAST) with MCP, Agent2Agent, and gRPC support. Released their Agentic Roadmap in January. Their approach wraps existing protocols rather than building new ones.
There's tension between these two efforts. AdCP is purpose-built for agent-to-agent transactions. IAB Tech Lab is retrofitting existing infrastructure. Both have legitimacy. The outcome will determine whether Layer 2 operates on bespoke agent standards or through adapted programmatic plumbing.
For developers building MCP servers today, the practical impact is limited. Neither standard mandates a specific integration pattern at the tool level. You can integrate ad revenue now and adapt to whichever standard wins.
What This Means If You Build MCP Tools
The 95% of MCP servers that earn nothing represent untapped supply-side inventory. The developers who maintain these servers have already shown they can build things people use. They just haven't added a revenue layer because the options were either too complex (billing infrastructure) or non-existent (no ad network for MCP).
Layer 2 fills that gap with a model developers already understand: free tool, ad-supported, revenue share. It's the same model that funds most of the consumer web. Applied to tool calls instead of page views.
The window for establishing Layer 2 infrastructure is open. The big platform companies (Amazon, Meta, Google) are focused entirely on Layer 1 - making their existing ad businesses agent-friendly. They could extend into Layer 2 eventually, but right now, they're solving a different problem.
Getting Started with Layer 2
If your MCP server recommends products, services, or tools, you're a candidate for Layer 2 monetization.
const result = await ads.searchAds({
context: "CI/CD tool for monorepo",
keywords: ["CI", "CD", "pipeline", "build"],
});
if (result.ad) {
sponsoredOption = `\n\n[Sponsored] ${result.ad.content}`;
}
18 lines of TypeScript. Fails silently if no match. Revenue in USDC on Base.
npm install agentic-ads
First 10 publishers get 90/10 revenue share for 3 months.
Sources: Amazon Ads blog, GlobeNewswire (Dstillery), Magnite blog, IAB Tech Lab, AdCP spec, PubMatic case study, eMarketer. All claims from public reporting as of March 2026.
Top comments (0)