Glossary
What Is the Ad Context Protocol (AdCP)?
The Ad Context Protocol (AdCP) is an open industry standard that defines how AI agents communicate to plan, buy, and sell advertising. Stewarded by AgenticAdvertising.org and running on the Model Context Protocol (MCP) as its transport layer, it gives buyer agents and seller agents a shared schema for briefs, proposals, media buys, creatives, governance, and delivery data. AdCP is sometimes misexpanded as "Ad Commerce Protocol"; the correct name is Ad Context Protocol.
AdCP exists because agent-to-agent commerce needs a common language. Without it, every buyer agent would need a bilateral, custom integration with every seller platform, exactly the fragmentation that made legacy ad operations slow and expensive.
What does AdCP actually standardize?
The full lifecycle of an agentic media transaction, expressed as protocol tasks any compliant agent can call. A buyer agent dispatches a natural language brief to all certified sellers at once, receives proposals in one standard schema, executes a buy, syncs creatives, passes governance checks before spend, and retrieves delivery and pacing data in a consistent format. A media buy across multiple sellers takes one integration instead of many.
How does AdCP relate to MCP?
AdCP is the advertising-specific standard; the Model Context Protocol (MCP) is the general-purpose transport it runs on. MCP defines how AI systems connect to tools and exchange structured requests; AdCP defines what those requests mean in an advertising transaction. The relationship mirrors HTTP carrying many application protocols. For how MCP is used across the ad stack, see MCP advertising.
How is AdCP different from OpenRTB?
OpenRTB standardizes millisecond impression auctions; AdCP standardizes goal-driven transactions between agents. OpenRTB remains the plumbing of real-time bidding, and AdCP does not replace it impression by impression. AdCP operates a level above: briefs, negotiated proposals, guaranteed and non-guaranteed buys, and outcome feedback loops OpenRTB was never designed to carry.
Who uses AdCP today?
Adoption spans sell-side infrastructure, clearinghouses, and buy-side platforms. FreeWheel built an Ad Context Protocol server used in the first MCP-based agent-to-agent media buy with NBCUniversal in January 2026. Open-source sell-side agents and AdCP clearinghouses route certified inventory to compliant buyers. Adgentek is a Founding Member of AdCP through AgenticAdvertising.org, and the Adgentek Agentic Ad Server represents AI surface inventory, including the Spark conversational format, to AdCP-compliant buyers. Publishers can open their AI surfaces to this demand, and brands can reach it when they advertise in AI chatbots.
Why does AdCP matter for advertisers?
It removes the bilateral integration tax and compresses the fee stack between buyer and seller. When agents transact directly over a shared protocol, proposals arrive in comparable form, execution is immediate, and more of each budget dollar reaches working media instead of intermediary fees. That efficiency is a core reason agentic advertising is displacing dashboard-driven workflows. The first campaigns transacting this way reported 40-50% supply chain cost reductions, collected in our H1 2026 data report.
Common questions
What is the Ad Context Protocol?
The Ad Context Protocol (AdCP) is an open industry standard that defines how AI buying agents and AI selling agents communicate to transact advertising. It is stewarded by AgenticAdvertising.org and runs on the Model Context Protocol (MCP) as its transport layer.
Who owns AdCP?
No single company. It is an open industry consortium protocol stewarded by AgenticAdvertising.org, with founding members across the advertising ecosystem, including Adgentek.
What is the difference between AdCP and OpenRTB?
OpenRTB standardizes real-time impression auctions between DSPs and SSPs. AdCP standardizes agent-to-agent transactions: briefs, proposals, media buys, creative sync, governance, and delivery reporting, expressed in schemas AI agents can negotiate over directly.
Build on the open standard.
