Published: 17 September 2026

TL;DR: Publishers set deal terms for autonomous buying agents through a sell-side mandate: a human-approved governance document that defines the parameters within which the sell-side agent can act. A well-structured mandate covers CPM floors, inventory categories, deal type parameters, audience data permissions, and buyer category restrictions. Publishers need a mandate in place before deploying a sell-side agent, because without one the agent has no governed basis for accepting or rejecting proposals.

The arrival of autonomous buying agents creates a new operational requirement for publishers. When a human media buyer requested a deal, the publisher's team could evaluate the request in the context of the relationship, the buyer's history, and their own commercial priorities. Autonomous agents do not have relationships. They send proposals structured according to protocol standards and expect a structured response.

Publishers need a mechanism that translates their commercial priorities into parameters a sell-side agent can evaluate programmatically. That mechanism is the sell-side mandate.

What a Mandate Is

A mandate is a human-approved governance document that defines the parameters within which an agent can act autonomously. For a sell-side agent, the mandate is the document that tells the agent what it can accept, what it must reject, and what it must escalate for human review.

The mandate is written and approved by the publisher's team. It is not set by the marketplace or by the technology provider running the sell-side agent. The publisher owns the mandate. The publisher can update it. The sell-side agent operates within its constraints.

This ownership structure is what gives publishers control over how their inventory is sold to autonomous agents. The mandate is not a set of platform configurations buried in a DSP interface. It is a governance document that the publisher's team can read, approve, and revise.

What a Well-Structured Mandate Covers

A sell-side mandate for publisher inventory should address the following areas.

CPM floors by inventory category are the foundation. The mandate sets the minimum CPM the sell-side agent can accept for each category of inventory. Video inventory, display inventory, and premium contextual placements may have different floors. The mandate specifies each one. The sell-side agent will not accept a proposal below the relevant floor.

Inventory category permissions define which properties and placements the sell-side agent can include in deals. A publisher may want to restrict certain premium placements from being included in agent-negotiated deals until they have more experience with the model. The mandate specifies which categories are available and any conditions that apply.

Deal type parameters define the types of deals the sell-side agent can negotiate. Preferred deals, private marketplace deals, and programmatic guaranteed deals each have different operational implications. The mandate specifies which deal types the agent can accept and any volume or duration constraints.

Audience data permissions define what audience data the sell-side agent can represent in deal negotiations. If the publisher has first-party audience data, the mandate specifies under what conditions that data can be offered as part of a deal and what disclosures must accompany it.

Buyer category restrictions define which buyer categories the sell-side agent will deal with. A publisher may have policies against accepting deals from certain advertiser categories: competitors, restricted sectors, or categories that conflict with editorial standards. The mandate encodes these policies so the agent applies them automatically.

What Happens When a Proposal Falls Outside the Mandate

When a buy-side agent sends a proposal that falls outside the sell-side mandate parameters, the sell-side agent has three possible responses depending on how the mandate is structured.

Automatic rejection applies to proposals that clearly fall outside parameters with no ambiguity. A proposal with a CPM below the relevant floor is rejected automatically. The buy-side agent receives a rejection and can revise its proposal.

Counter-proposal applies where the mandate permits the sell-side agent to negotiate within a range. If the proposed CPM is below the floor but within a negotiable band, the sell-side agent can counter with the floor CPM. This allows deals to be reached without human involvement for minor discrepancies.

Escalation applies to proposals that raise questions the mandate does not resolve. A proposal from a buyer category the mandate does not address, or for a deal type with unusual conditions, may require a human publisher decision. The sell-side agent flags the proposal and pauses until the publisher's team provides a decision.

Why Publishers Need a Mandate Before Deploying

A sell-side agent without a mandate has no governed basis for its decisions. It is either constrained to doing nothing or making decisions without the parameters the publisher's team has approved.

The mandate is not an optional enhancement. It is the governance foundation of the sell-side agent. A publisher deploying a sell-side agent without a mandate is operating an autonomous system without the oversight structure that makes autonomous operation acceptable.

Publishers should treat mandate construction as the first step in sell-side agentic deployment, not an afterthought. The quality of the mandate determines the quality of the deals the agent accepts. A mandate written carelessly will produce deals the publisher's team would not have accepted if they had reviewed each one manually.