Agentic Buying

Agentic buying is media procurement performed by software agents. A buyer agent states what a campaign needs, a seller agent replies with products and prices, and the two agree a media buy without human intervention at each step. The unit that changes hands is a booked buy agreed between two parties rather than an impression won against a bid.

AdCP’s FAQ gives the term its only definition in either specification corpus, with the same scope: “how a buyer agent and a seller agent negotiate, transact, and govern a media buy across product discovery, pricing, creative, signals, and governance.”

That same answer draws the line between the two agentic advertising stacks — “AAMP is agentic bidding; AdCP is agentic buying” — a characterisation AdCP qualifies as “based on AAMP materials published to date”, alongside “we do not yet publish a formal technical comparison because AAMP is still defining its normative surface”. Neither phrase appears in the AAMP repositories, and AdCP’s glossary carries neither the term nor agentic advertising.

Where the context sits at decision time

In AdCP’s training material for decision makers, programmatic “sends thin signals out to a remote bidder without context”, while agentic advertising “brings rich data in to the platform that holds the context and generates the response”. A bid request carries a page URL, a device type and perhaps an identifier; the retailer, the CTV app or the assistant receiving it already holds the basket, the purchase history and the session. Agentic buying pushes brand rules, goals and product catalogue into that party instead of pulling a thin request out of it.

An end-to-end walkthrough of the transaction, before any protocol vocabulary, is at whatisagenticbuying.com.

Where each stack sits relative to the auction

AdCP’s total is one release; the AAMP total spans nine independently versioned repositories, so the totals are not equivalent. What compares is the share of each stack that runs at serve time: two operations of 64 on one side, one of 143 on the other.

Both of AdCP’s impression-layer operations belong to the Trusted Match Protocol. None of the 48 schemas in AAMP’s shared wire contract describes a bid; they describe Order, Line, Quote, Deal, Negotiation, Proposal, ChangeRequest and RateCard. Order.json describes itself as a “Campaign container (insertion order) holding one or more lines”, and the seller agent’s README describes that project as “An AI-powered inventory management system for publishers and SSPs to automate programmatic deal negotiation, booking, and distribution using IAB Tech Lab standards.” The only bid-shaped field in those 48 schemas is bidfloor, on Deal.json and on the booking response that embeds it, which “adapters translate to the raw OpenRTB float … at the DSP edge”. AdCP’s FAQ describes the same relationship when it says one create_media_buy can spawn thousands of impression-layer events.

ARTF is the one AAMP repository the agentic-bidding label fits and the only AAMP artifact stamped Version 1.0 FINAL, while iab-agentic-primitives, the repository carrying those 48 schemas, is neither linked from the hub README nor released. Both reference agents pin it as their wire contract. Whether that makes AAMP a bid-request mutation stack or a booking stack is argued at Agentic Ad Lab.

What agentic buying is not

Google’s Universal Commerce Protocol (UCP) and the Agentic Commerce Protocol (ACP) from OpenAI and Stripe standardise payment and fulfilment inside AI assistants; neither books media, and AdCP’s FAQ files them under commerce in a separate answer. A conversational front end on a demand-side platform is a separate case: agentic buying requires a machine counterparty rather than a machine interface, and a chat window over a DSP leaves the buy assembled and executed by the same system, with the human in the same place.

The two object vocabularies — media buy, or Order and Line — are set side by side on the terminology map.