Published: 17 September 2026

TL;DR: Publishers need three things before they can accept deals from autonomous buying agents: AdCP-compliant integration so their systems can receive and parse structured proposals; a sell-side mandate that defines the parameters for autonomous acceptance; and deal record infrastructure so agreed terms are written to a DealSheet the publisher can retrieve independently. The most common readiness gap in 2026 is the mandate: publishers have the technical integration but have not done the governance work.

The volume of buy-side agent activity in the market is increasing. Publishers who have not prepared their systems to receive and evaluate structured proposals from autonomous agents are already missing deal opportunities. More significantly, publishers deploying sell-side agents without the right governance foundations are accepting deals on terms their teams have not properly reviewed.

This piece sets out the three requirements for publisher readiness and explains where the most common gaps lie.

Requirement One: AdCP-Compliant Integration

The first requirement is technical. AdCP, the AdCP, published by AgenticAdvertising.org, is the standard that defines how buy-side and sell-side agents communicate. A buy-side agent sends a deal proposal structured according to AdCP. A sell-side system that is not AdCP-compliant cannot parse that proposal correctly.

AdCP compliance means the publisher's systems (or the SSP the publisher uses) can receive a structured proposal from any AdCP-compliant buy-side agent, parse it into the fields the sell-side agent needs to evaluate, and send a structured response that the buy-side agent can interpret.

Without AdCP compliance, the publisher is invisible to autonomous buying agents operating through the standard protocol. Buy-side agents will not attempt to negotiate with systems they cannot communicate with.

The integration work for AdCP compliance varies depending on the publisher's existing technical infrastructure. Publishers using SSPs that have already built AdCP-compliant sell-side capabilities can connect through that integration. Publishers with direct tech stacks will need to build or procure the integration separately.

Requirement Two: A Sell-Side Mandate

The second requirement is governance. A sell-side mandate is the human-approved document that defines the parameters within which the sell-side agent can accept deals autonomously.

Without a mandate, the sell-side agent has no governed basis for its decisions. It cannot accept a proposal at the right CPM if no floor has been set. It cannot restrict buyer categories if those restrictions have not been specified. It cannot protect premium inventory from being included in deals the publisher would not sanction.

A mandate covers CPM floors by inventory category, deal type permissions, inventory category parameters, audience data permissions, and buyer category restrictions. It is written and approved by the publisher's team. The sell-side agent evaluates every incoming proposal against the mandate and accepts, rejects, or escalates accordingly.

The mandate must be reviewed and updated as the publisher's commercial priorities change. A mandate set at deployment and never revised will over time reflect the publisher's priorities at a single point in time, not their current commercial position.

Requirement Three: Deal Record Infrastructure

The third requirement is operational. The publisher needs deal record infrastructure: the capability to receive a DealSheet at the moment of agreement and store it in a format that can be retrieved and compared against delivery data later.

A DealSheet is the bilateral record of agreed terms written by the marketplace when the buy-side and sell-side agents reach agreement. The publisher's systems need to receive this record, store it, and be able to retrieve it at reconciliation or dispute resolution.

Publishers who do not have DealSheet infrastructure are accepting deals without a pre-delivery record of what was agreed. They are in the same position as conventional programmatic buyers: reliant on post-campaign logs to establish what the deal contained. This is a significant operational disadvantage, particularly if a dispute arises.

The deal record infrastructure requirement is usually met by connecting to a marketplace that provides bilateral DealSheet storage. The marketplace writes the record; both parties receive it. The publisher needs systems that can accept and store that record, not necessarily systems that generate it.

The Most Common Readiness Gap

The most common publisher readiness gap in 2026 is the mandate. Most publishers working with SSPs that have built AdCP capabilities have the first requirement covered. Many have connected to marketplaces that provide deal record infrastructure, so the third requirement is partially addressed.

The governance gap is the persistent one. Building a mandate requires the publisher's commercial, legal, and operations teams to agree on deal parameters. This is not a technical task. It requires the organisation to make explicit decisions about CPM floors, buyer category restrictions, audience data policies, and deal type permissions that were previously handled case by case in individual negotiations.

Publishers who have not done this work are either unable to deploy a sell-side agent at all, or deploying one that operates without meaningful governance. Neither outcome serves the publisher's commercial interests.

The practical priority for publishers preparing to accept agent-negotiated deals is to start with the mandate. Get the governance document written and approved. The technical integration work can run in parallel; the governance work is the dependency that most commonly delays readiness.