TL;DR: A machine-readable ad deal for agent-to-agent negotiation is a structured document in which every deal parameter is expressed in a format that an agent can evaluate programmatically, without ambiguity. It captures party identities, inventory parameters, CPM terms, audience data conditions, delivery commitments, and approval thresholds in a schema that both the buying agent and the selling agent can parse, evaluate, and sign off on without human intervention at each step.

The phrase "machine-readable" is often applied loosely in advertising to mean "digital" or "in a system." A machine-readable deal in the agent-to-agent context has a more precise meaning: every parameter is expressed in a format that a software agent can evaluate against its mandate instructions without needing to interpret ambiguous natural language.

A conventional IO (insertion order) is a human-readable document. It states that the buyer will purchase 10 million impressions at a £5 CPM on premium news content. A human reads this and understands what it means. A software agent cannot evaluate this against a mandate unless "premium news content" is translated into a machine-parseable inventory specification, and "£5 CPM" is expressed as a numeric value within a currency-denominated range that the agent can compare against its authorised parameters.

Machine-readable deal structure is what makes autonomous agent-to-agent negotiation possible.

The core fields of a machine-readable deal

A deal structured for agent-to-agent negotiation under AdCP (Agent Communication Protocol), published by AgenticAdvertising.org specification will contain several categories of field.

Party identifiers. Both the buying agent and the selling agent are identified by verifiable credentials that name the principal they represent, the marketplace they are operating through, and the mandate authority under which they are acting. These identifiers are not free-text names; they are structured credential references that can be verified against a registry.

Inventory specification. The inventory the deal covers is expressed in structured parameters: domain lists or domain categories, ad placement types, ad format specifications, and any exclusion lists. A sell-side agent evaluates this inventory specification against the publisher's available inventory to determine whether there is a match. A buy-side agent evaluates it against the buyer's mandate to confirm the proposed inventory falls within the buyer's authorised scope.

CPM terms. The price is expressed as a numeric value or range within a specified currency and billing unit. The buy-side agent's mandate defines the CPM range within which the agent can accept; the sell-side agent's mandate defines the CPM floor below which the agent cannot go. Machine evaluation of CPM terms is straightforward: the proposed CPM either falls within both parties' ranges, or it does not.

Audience data conditions. Any use of audience data by the buyer is expressed as a structured permission set: what data the buyer will bring to targeting, whether any data will be shared with the publisher, and what data protection conditions apply to the use of that data. These conditions need to be machine-evaluable so the sell-side agent can verify them against the publisher's data policy without a human legal review of each deal.

Delivery commitment. The volume commitment, if any, is expressed as a numeric quantity with a defined measurement unit and a tolerance range. The DealSheet captures what was committed; delivery data is compared against it post-campaign.

Approval thresholds. The deal structure includes the financial and scope thresholds at which either agent must escalate to a human before proceeding. A buy-side agent instructed not to agree deals above a certain total value without human approval will have that threshold expressed as a numeric value in the deal structure; the agent checks the deal total against this value before accepting.

Why structure matters for negotiation speed

Machine-readable deal structure enables the negotiation to proceed at agent speed. When every parameter is in a format that the agent can evaluate in milliseconds, a full negotiation cycle from initial proposal to bilateral agreement can complete in seconds. When deal parameters are expressed ambiguously, or are missing from the structured format, the agent cannot evaluate them autonomously and must escalate to a human, eliminating the speed advantage.

This means that deal structure quality directly affects how much of the negotiation can be autonomous. A well-structured deal proposal that covers all parameters the sell-side agent needs to evaluate will result in an autonomous response. A proposal that is missing a required field, or that expresses a parameter in a format the sell-side agent cannot parse, will either be rejected automatically or will require a human to complete the missing information.

The DealSheet as the completed deal record

Once both parties reach agreement, the agreed parameters are consolidated into the DealSheet: the bilateral deal record that both parties hold in shared state. The DealSheet is not a summary of the negotiation; it is the authoritative, machine-readable record of every agreed term. It can be retrieved, parsed, and compared against delivery data by either party independently of the counterparty, at any point during or after the campaign.

The DealSheet is what makes post-campaign audit possible at machine speed. A buyer or publisher with an automated reconciliation process can compare delivery data against the DealSheet without requiring a human to cross-reference documents. The structure that made negotiation possible also makes audit efficient.