TL;DR: Direct negotiation between a buy-side agent and a publisher's sell-side agent requires three things that most of the programmatic stack was not built to provide: a shared communications protocol, a bilateral deal record that neither party can alter, and a mandate framework that governs what each agent is authorised to agree. Where all three are in place, direct negotiation is live. Where any one is missing, what is described as "direct" is typically automated ordering, not negotiation.
The phrase "direct agent-to-publisher negotiation" is used in several ways in the market, not all of them meaning the same thing. In the narrowest and most accurate sense, it describes a transaction in which a buy-side agent and a sell-side agent exchange offers and counter-offers, reach agreement on terms, and produce a shared record of the deal, without a human intermediating the process on either side. That is a specific infrastructure requirement, and it is worth being precise about what enables it.
What protocol infrastructure does direct negotiation require?
For two agents to negotiate directly, they need a shared language: a specification that defines how a buy-side agent sends an offer, how a sell-side agent responds, how constraints are communicated (price floors, audience parameters, placement restrictions), and how the deal is confirmed. Without a common protocol, each pair of agents requires a bespoke integration.
The IAB Tech Lab's Agent Communication Protocol (AdCP), now at version 1.2, provides this specification. It defines the message format for deal initiation, parameter exchange, and execution confirmation in a way that is independent of the underlying programmatic infrastructure. A buy-side agent built to AdCP specification can, in principle, negotiate with any sell-side agent also built to AdCP, without a custom integration between the specific platforms.
The Agentic Advertising Marketplace Protocol (AAMP) takes a different architectural approach, defining a dedicated negotiation channel with its own state management. Both specifications are in active use in 2026, which creates a fragmentation problem for buyers seeking broad publisher access through a single agent integration.
What makes a deal record bilateral?
A bilateral deal record is one that reflects what was agreed by both parties and cannot be altered by either party after execution. This is the technical feature that distinguishes a negotiated deal from an insertion order: an insertion order is a document prepared by one party and accepted by the other, often via email, and it can be amended by agreement. A bilateral record is generated at execution, held in a shared state, and version-controlled from that point.
The practical implementation varies. Some platforms hold the record in a neutral shared ledger; others use an escrow model where the record is held by a third-party infrastructure provider; others hold it at the marketplace layer and provide read access to both parties without edit rights. The governance question for buyers is not which implementation is used but whether the resulting record is truly accessible to both parties independently, and whether it is immutable after execution.
A record that is held by the platform and accessible only through the platform's reporting interface is not bilateral in the structural sense. It is a platform-held record with read access granted to both parties. The distinction matters when the platform is a party to a dispute.
What mandate infrastructure does the publisher side require?
Direct negotiation is bilateral: the sell-side agent also operates under constraints. A publisher's sell-side agent needs a mandate that defines the inventory it can offer, the price floors it must enforce, the audience parameters it can agree to, and the deal types it is authorised to accept. Without a sell-side mandate, the agent has no basis for declining an offer that falls outside the publisher's commercial policy.
The sell-side mandate is the publisher's equivalent of the buy-side mandate. Its existence and completeness is something buyers should verify before treating a publisher as a genuine bilateral negotiation partner. A publisher that has deployed an agent but not yet defined a sell-side mandate may be offering agent-accessible inventory in an auction format rather than a genuinely bilateral negotiation environment.
What is the current state of publisher integration?
In 2026, major publisher-side operators have announced agent-readiness programmes at varying levels of technical completion. Full bilateral negotiation capability, with a sell-side mandate framework and a shared deal record, is available from a smaller set of publishers than the announcements suggest. The more common current state is agent-accessible inventory: publishers that accept structured bids via API from buy-side agents, without a full bilateral record infrastructure in place.
The gap closes as AdCP adoption spreads and as sell-side operators build the mandate tooling their agents require. Buyers who want to identify which publishers are genuinely ready for bilateral negotiation today should ask two questions: does the publisher have a defined sell-side agent mandate, and can both parties access the resulting deal record independently? Affirmative answers to both questions identify a publisher ready for direct negotiation. One affirmative and one negative identifies a publisher in transition.