Agentic Advertising

Agent-ready ad infrastructure: what AAMP, AdCP and agentic AI in programmatic advertising need from your stack

Published November 10, 2026 · Last updated November 10, 2026
Next scheduled review: 9 December 2026

Agent-ready ad infrastructure is an ad platform that AI agents can find, understand and transact with safely. In practice it means machine-readable products and deals, a Model Context Protocol (MCP) or Agent2Agent (A2A) endpoint, a registry listing, real authentication, spend guardrails and audit logs. IAB Tech Lab's Agentic Advertising Management Protocols (AAMP) and AdCP define most of these pieces.

Contents

Key facts

AAMP 2.3 made human approval part of the reference agents. IAB Tech Lab's 30 July 2026 release says "any path that commits spend is deterministic and provable with human approvals outside of value-based thresholds" (IAB Tech Lab, 30 July 2026).
It also fixed agents that made up prices. PPC Land reports that AAMP 2.3 adds a pricing provenance field to stop what IAB Tech Lab calls "CPM hallucination", invented cost-per-thousand (CPM) prices (PPC Land, 30 July 2026).
The next layer is still a draft. AAMP 3.0 introduced OpenProposal for the request-for-proposal (RFP) stage on 22 September 2026, and IAB Tech Lab extended its public comment period to 10 November 2026 (IAB Tech Lab, 22 September 2026).
AdCP plans to require signed requests for spending money. The Ad Context Protocol's documentation lists RFC 9421 request signing as optional in 3.x and "required for spend-committing operations" in 4.0, targeted for early 2027 (AdCP docs, authentication, 3.2.8).
Registries exist but are small. The IAB Tech Lab registry listed 53 entries on 9 November 2026 (IAB Tech Lab registry). AgenticAdvertising.org's registry counted 35 enrolled agents that day (AgenticAdvertising.org registry stats, 9 November 2026).

Jump to the table

Definition

Agent-ready ad infrastructure: advertising technology that publishes its inventory, prices, deals and permitted actions through documented machine-readable interfaces, and that authenticates, limits, approves and logs every action a software agent takes through those interfaces. See the glossary entries for agentic advertising, AAMP and AdCP.

Being agent-ready is not the same as having an AI feature. A platform can run a chatbot and still be closed to outside agents. It can also have no AI at all and be fully ready, because its catalogue, deals and orders are reachable through clean, guarded APIs. This page belongs to the agentic advertising hub.

What agentic AI in programmatic advertising asks of a platform

An agent does three things with your system. It discovers what you sell. It negotiates or books a buy. And it checks what happened afterwards. Each step needs something a human-only workflow could skip.

Discovery needs structured descriptions. A human reads a PDF media kit; an agent needs fields it can compare. Booking needs an API that confirms an order once, even if the agent retries. Checking needs delivery data the agent can match to what it bought. Agents also make mistakes at machine speed, so every step needs limits and a record.

The money moving through agents is still small. Our AAMP vs AdCP tracker follows the adoption evidence month by month, and AI agents for media buying covers what agencies run today. The point of preparing now is that the hard parts, such as authentication, guardrails and logging, take longer to build than the agent itself.

The agent-readiness checklist

The table is the core of this page. Each row is one capability, the standard that covers it, its status on the date of the last update and the source. "Shipped" means a published version exists. "Proposal" means a draft, a public comment version or a stated plan.


1	Readable product catalogue	Products, formats, audiences and prices as structured data	AdCP `get_products`; IAB OpenProposal (AAMP 3.0)	AdCP 3.2 shipped (GA 30 Sep 2026); OpenProposal is a proposal (v3.0-draft-1, comment to 10 Nov 2026)	AdCP versioning; IAB Tech Lab, 22 Sep 2026
2	Shared vocabulary	The same IDs for formats, placements and categories	AdCOM 1.0	Shipped	AdCOM on GitHub
3	Deals an agent can read and sync	Deal terms in a standard object, synced between SSP and DSP	OpenRTB 2.6 `pmp.deals`; IAB Deals API v1.0	OpenRTB shipped (2.6-202606, 11 Jun 2026); Deals API v1.0 out for comment 4 Dec 2025, final status n/d	openrtb2.x releases; IAB Tech Lab, 4 Dec 2025
4	Guaranteed orders by API	Orders and lines created and changed through an API	OpenDirect 2.1	Shipped (8 Jul 2024); AAMP 2.3 agents conform to it (30 Jul 2026)	OpenDirect releases; IAB Tech Lab, 30 Jul 2026
5	Tool endpoint for AI models	An MCP server exposing your actions as tools	Model Context Protocol, revision 2026-07-28	Shipped (28 Jul 2026)	MCP releases
6	Agent-to-agent endpoint	Tasks other agents can delegate to yours	Agent2Agent (A2A) v1.0	Shipped (v1.0.0 on 12 Mar 2026; v1.0.1 on 28 May 2026)	A2A releases
7	Discovery files	Public files saying who you are and which agents act for you	A2A agent card at `/.well-known/agent-card.json`; AdCP `brand.json` and `adagents.json`	Shipped	A2A specification; AdCP seller verification
8	Registry listing	Entry with legal name, verified domain and live endpoint	IAB Tech Lab Agent & MCP Server Registry; AgenticAdvertising.org registry	Shipped (IAB registry live 3 Mar 2026; 53 entries on 9 Nov 2026)	IAB Tech Lab roadmap letter; IAB Tech Lab registry; AAO stats
9	Proof of authority to sell	Evidence that a seller agent may sell the inventory it offers	AdCP `adagents.json`; IAB "ads.txt for agents"	AdCP shipped; IAB version is a roadmap item (4 Mar 2026), a proposal	AdCP seller verification; IAB Tech Lab, 4 Mar 2026
10	Authentication	Credentials tied to an account; stronger proof for spend	MCP authorization (OAuth 2.1); AdCP bearer, mTLS or RFC 9421 signatures	MCP shipped; AdCP signatures optional in 3.x, required for spend in 4.0 (target early 2027), a proposal	MCP authorization, 2026-07-28; AdCP authentication
11	Idempotent orders	A retried order books once	AdCP `idempotency_key`; AAMP 3.0 SDK hardening	AdCP shipped (3.x); AAMP 3.0 work in comment (22 Sep 2026)	AdCP, calling an agent; IAB Tech Lab, 22 Sep 2026
12	Spend caps and human approval	Hard limits; a person approves above a threshold	AAMP 2.3 Buyer and Seller Agents; AdCP governance (`check_governance`)	AAMP 2.3 shipped (30 Jul 2026); AdCP governance shipped as a hook the seller must wire up	IAB Tech Lab, 30 Jul 2026; AdCP trust
13	Pricing integrity	Every price traces to a real source; unknown prices stay empty	AAMP 2.3 pricing provenance; Seller Agent v2.3.2	Shipped in the reference agents (29 to 30 Jul 2026)	PPC Land, 30 Jul 2026; seller-agent releases
14	Privacy diligence before a deal	Vendor checks run before data or money moves	AAMP 2.3 IAB Diligence Platform and SafeGuard Privacy gate	Shipped, off by default (30 Jul 2026)	IAB Tech Lab, 30 Jul 2026
15	Audit log	Every tool call and decision recorded with inputs and outputs	AdCP `get_plan_audit_logs`; AAMP seller agent event log	AdCP shipped (3.x); seller agent `GET /events` in v2.4.0 (4 Aug 2026)	AdCP trust; seller-agent releases
16	Bidstream extensions (optional)	Agent enrichment or audience signals inside the auction	ARTF v1.0; Agentic Audiences v1.1	ARTF v1.0 tagged 20 Jul 2026; Agentic Audiences v1.1 released Aug 2026	ARTF releases; IAB Tech Lab standards page

1

Capability: Readable product catalogue
What "ready" looks like: Products, formats, audiences and prices as structured data
Standard or spec: AdCP get_products; IAB OpenProposal (AAMP 3.0)
Status (date): AdCP 3.2 shipped (GA 30 Sep 2026); OpenProposal is a proposal (v3.0-draft-1, comment to 10 Nov 2026)

2

Capability: Shared vocabulary
What "ready" looks like: The same IDs for formats, placements and categories
Standard or spec: AdCOM 1.0
Status (date): Shipped

3

Capability: Deals an agent can read and sync
What "ready" looks like: Deal terms in a standard object, synced between SSP and DSP
Standard or spec: OpenRTB 2.6 pmp.deals; IAB Deals API v1.0
Status (date): OpenRTB shipped (2.6-202606, 11 Jun 2026); Deals API v1.0 out for comment 4 Dec 2025, final status n/d

4

Capability: Guaranteed orders by API
What "ready" looks like: Orders and lines created and changed through an API
Standard or spec: OpenDirect 2.1
Status (date): Shipped (8 Jul 2024); AAMP 2.3 agents conform to it (30 Jul 2026)

5

Capability: Tool endpoint for AI models
What "ready" looks like: An MCP server exposing your actions as tools
Standard or spec: Model Context Protocol, revision 2026-07-28
Status (date): Shipped (28 Jul 2026)

6

Capability: Agent-to-agent endpoint
What "ready" looks like: Tasks other agents can delegate to yours
Standard or spec: Agent2Agent (A2A) v1.0
Status (date): Shipped (v1.0.0 on 12 Mar 2026; v1.0.1 on 28 May 2026)

7

Capability: Discovery files
What "ready" looks like: Public files saying who you are and which agents act for you
Standard or spec: A2A agent card at /.well-known/agent-card.json; AdCP brand.json and adagents.json
Status (date): Shipped

8

Capability: Registry listing
What "ready" looks like: Entry with legal name, verified domain and live endpoint
Standard or spec: IAB Tech Lab Agent & MCP Server Registry; AgenticAdvertising.org registry
Status (date): Shipped (IAB registry live 3 Mar 2026; 53 entries on 9 Nov 2026)

9

Capability: Proof of authority to sell
What "ready" looks like: Evidence that a seller agent may sell the inventory it offers
Standard or spec: AdCP adagents.json; IAB "ads.txt for agents"
Status (date): AdCP shipped; IAB version is a roadmap item (4 Mar 2026), a proposal

10

Capability: Authentication
What "ready" looks like: Credentials tied to an account; stronger proof for spend
Standard or spec: MCP authorization (OAuth 2.1); AdCP bearer, mTLS or RFC 9421 signatures
Status (date): MCP shipped; AdCP signatures optional in 3.x, required for spend in 4.0 (target early 2027), a proposal

11

Capability: Idempotent orders
What "ready" looks like: A retried order books once
Standard or spec: AdCP idempotency_key; AAMP 3.0 SDK hardening
Status (date): AdCP shipped (3.x); AAMP 3.0 work in comment (22 Sep 2026)

12

Capability: Spend caps and human approval
What "ready" looks like: Hard limits; a person approves above a threshold
Standard or spec: AAMP 2.3 Buyer and Seller Agents; AdCP governance (check_governance)
Status (date): AAMP 2.3 shipped (30 Jul 2026); AdCP governance shipped as a hook the seller must wire up

13

Capability: Pricing integrity
What "ready" looks like: Every price traces to a real source; unknown prices stay empty
Standard or spec: AAMP 2.3 pricing provenance; Seller Agent v2.3.2
Status (date): Shipped in the reference agents (29 to 30 Jul 2026)

14

Capability: Privacy diligence before a deal
What "ready" looks like: Vendor checks run before data or money moves
Standard or spec: AAMP 2.3 IAB Diligence Platform and SafeGuard Privacy gate
Status (date): Shipped, off by default (30 Jul 2026)

15

Capability: Audit log
What "ready" looks like: Every tool call and decision recorded with inputs and outputs
Standard or spec: AdCP get_plan_audit_logs; AAMP seller agent event log
Status (date): AdCP shipped (3.x); seller agent GET /events in v2.4.0 (4 Aug 2026)

16

Capability: Bidstream extensions (optional)
What "ready" looks like: Agent enrichment or audience signals inside the auction
Standard or spec: ARTF v1.0; Agentic Audiences v1.1
Status (date): ARTF v1.0 tagged 20 Jul 2026; Agentic Audiences v1.1 released Aug 2026

Download JSON

Table by AdSovereign, CC BY 4.0.

The first seven rows decide whether an agent can find and understand you. The next four decide whether it can trust you and act once. The last group decides whether you can trust the agent. Most teams start at the top, but the bottom rows are where the risk sits.

Machine-readable inventory and deal descriptions

A human buyer can read "premium homepage takeover, rates on request". An agent cannot. It needs each product as fields: format, placement, audience, flight dates, price model, price and how the buy will run.

Two specifications describe this today. AdCP's get_products task returns structured products; the protocol's current release is 3.2.9, tagged on 9 November 2026 (AdCP releases). IAB Tech Lab's answer is OpenProposal, the core of AAMP 3.0. It lets sellers publish packages, answer a buyer's brief and keep a link to the original offer through negotiation (IAB Tech Lab, 22 September 2026). PPC Land counted 71 fields in the draft, which states that "nothing here is a ratified IAB Tech Lab standard" (PPC Land, 25 October 2026).

You do not need to pick a side to start. Both reuse AdCOM values and both hand execution to existing rails. Clean product data is useful in either format. Begin with a catalogue that a script, not a person, can read.

Endpoints: MCP, A2A and discovery files

An agent reaches you through one of two protocols. The Model Context Protocol (MCP) exposes your actions as tools that a model can call, such as "list products" or "create a media buy". Its current stable revision is dated 28 July 2026 (MCP releases). Agent2Agent (A2A) lets one agent hand a task to another; version 1.0.0 shipped on 12 March 2026 (A2A releases).

Most advertising agents today use MCP. Of the 53 entries in the IAB Tech Lab registry on 9 November 2026, 52 used MCP and one used A2A (IAB Tech Lab registry). AAMP 2.3 restored Streamable HTTP as the main MCP transport, with the older Server-Sent Events kept for legacy clients (PPC Land, 30 July 2026).

Discovery files tell an agent who you are before it calls anything. An A2A agent publishes an agent card at /.well-known/agent-card.json (A2A specification). In AdCP, a company publishes brand.json, and a publisher lists the sales agents it authorises in /.well-known/adagents.json (AdCP, seller verification). AdCP keeps one call open to everyone: get_adcp_capabilities needs no credentials, so buyers can see what you offer before a contract exists (AdCP, authentication).

Registration: being findable and checkable

A registry turns an endpoint into a listed counterparty. IAB Tech Lab's Agent & MCP Server Registry has been live since 3 March 2026 and is free to join (IAB Tech Lab 2026 roadmap letter). AgenticAdvertising.org runs a second registry for AdCP agents. On 9 November 2026 it counted 35 enrolled agents and 93 more discovered through publishers' adagents.json files (AgenticAdvertising.org registry stats).

A listing proves less than it seems. The IAB registry checks domain ownership, a Global Privacy Platform (GPP) ID and endpoint health; it does not test what an agent does with a budget. What each agent registry field means, and the twelve checks a buyer should run, are in our guide to the IAB Tech Lab Agent Registry. One gap matters for sellers. IAB Tech Lab lists "ads.txt for agents" as a roadmap item, so its registry cannot yet prove that an agent may sell what it offers (IAB Tech Lab, 4 March 2026).

Authentication: who is calling, and may they spend?

Every protected call should map to a known account and a known set of permissions. MCP's authorization specification makes the MCP server an OAuth 2.1 resource server and the client an OAuth 2.1 client, citing the IETF's OAuth 2.1 draft (MCP authorization, 2026-07-28). On the IAB side, AAMP 2.3 replaced the Seller Agent's custom credential paths with OAuth (PPC Land, 30 July 2026).

AdCP explains why a token alone is weak for money. "A bearer token authenticates whoever presents it," its documentation says, so anyone who steals it can place orders (AdCP, authentication). Signed requests under RFC 9421 bind the payload to a private key and add a timestamp window of plus or minus 60 seconds against replay. AdCP 3.x accepts bearer tokens, mutual TLS or signatures. Version 4.0, targeted for early 2027, would make signatures mandatory for spend-committing operations.

A practical rule follows. Give read-only tools broad access and keep spending tools behind strong, account-bound credentials. Never let one shared key both browse the catalogue and create a buy.

Guardrails: budget caps, approvals and pricing data integrity

An agent with a budget needs three kinds of limits. Hard caps stop spend above a set amount. Approval thresholds send larger actions to a person. And data rules stop the agent from acting on numbers that are not real.

AAMP 2.3 built all three into the IAB reference agents. Paths that commit spend need human approval outside value-based thresholds, and "inventory availability is always based on real, not derived, numbers" (IAB Tech Lab, 30 July 2026). The pricing fix targets what IAB Tech Lab called "CPM hallucination": earlier agent versions could produce a made-up CPM when real pricing data was missing (PPC Land, 30 July 2026). A provenance field now records where each price came from.

The code shows the same fix. Seller Agent v2.1.1 made unknown availability figures null, "never invented". Version 2.3.2, released on 29 July 2026, made deal creation "require a real floor price (no fabricated defaults)" (IABTechLab/seller-agent releases). Retries are the other risk. AdCP requires an idempotency_key on create_media_buy and other changes, so a retried request cannot book twice (AdCP, calling an agent).

Platforms are adding their own controls. PubMatic's guardrails for its AgenticOS platform, announced on 5 August 2026, include budget thresholds, inventory allowlists and approvals confirmed with a one-time passcode (PPC Land, 5 August 2026). AdCP's governance agent is more limited by design. The specification calls check_governance "a seam, not an enforcer" (AdCP, trust and security).

Below is the kind of policy a platform can attach to each agent credential. The field names are ours, not from AAMP or AdCP, and the values are examples.

{
  "agent_id": "buyer-agent-retail-01",
  "account_id": "acct-4471",
  "allowed_tools": ["get_products", "get_media_buy_delivery", "create_media_buy", "update_media_buy"],
  "read_only_tools": ["get_products", "get_media_buy_delivery"],
  "spend_limits": { "currency": "USD", "per_order_max": 25000, "per_day_max": 100000 },
  "human_approval": { "required_above": 10000, "approver_role": "trading-lead", "expires_after_hours": 24 },
  "pricing_rules": { "require_price_source": true, "reject_if_price_missing": true, "max_cpm": 45.0 },
  "idempotency": { "required_on_writes": true, "key_ttl_hours": 72 },
  "audit_log": { "log_inputs": true, "log_outputs": true, "retention_days": 400 }
}

6 of 6 rows

Density


`allowed_tools`, `read_only_tools`	Least privilege: this credential can read freely but only some tools can write
`spend_limits`	Hard caps the platform enforces, whatever the agent asks
`human_approval`	Orders above the threshold wait for a named role; unapproved requests expire
`pricing_rules`	Refuse prices with no traceable source, the failure AAMP 2.3 targets
`idempotency`	Writes must carry a key; repeats return the original result
`audit_log`	Store inputs and outputs of every call for at least a full planning year

`allowed_tools`, `read_only_tools`

Purpose: Least privilege: this credential can read freely but only some tools can write

`spend_limits`

Purpose: Hard caps the platform enforces, whatever the agent asks

`human_approval`

Purpose: Orders above the threshold wait for a named role; unapproved requests expire

`pricing_rules`

Purpose: Refuse prices with no traceable source, the failure AAMP 2.3 targets

`idempotency`

Purpose: Writes must carry a key; repeats return the original result

`audit_log`

Purpose: Store inputs and outputs of every call for at least a full planning year

Download JSON

Table by AdSovereign, CC BY 4.0.

Audit logs: proving what the agent did

When an agent books the wrong thing, you need to answer three questions fast. Who asked? What exactly was sent? What did your system return? Only a log answers them.

AdCP makes governance decisions queryable: each one produces a get_plan_audit_logs entry, described as "immutable, timestamped, and reproducible". The IAB Seller Agent added an event log endpoint, GET /events, in version 2.4.0 on 4 August 2026 (IABTechLab/seller-agent releases). PubMatic says its system logs every agent action with what it did, when, under which parameters and whether a human was involved (PPC Land, 5 August 2026).

Treat agent logs like financial records. Keep them outside the agent's reach, tie each entry to the credential that made the call, and join them to delivery data. That join is easier if you already keep log-level data for your auctions. Under the EU AI Act some agent decisions may also need logging for oversight; the EU AI Act and advertising covers when.

How agent workflows map onto OpenRTB and OpenDirect

Agents negotiate; existing rails execute. Neither AAMP nor AdCP replaces the auction or the order system. The table shows where a typical agent action lands.

7 of 7 rows

Density


Agree a private marketplace deal	OpenRTB bid requests that carry the deal	`imp.pmp.deals[].id`, deal floor, allowed seats	OpenRTB 2.6
Book programmatic guaranteed	OpenRTB deal flagged as guaranteed	`Deal.guar = 1`; the IAB Seller Agent sets it "on the wire" from v2.3.2	seller-agent releases
Book a direct guaranteed order	Seller's order management system	OpenDirect 2.1 orders and lines	OpenDirect releases
Sync deal terms to DSPs	SSP to DSP deal sync	IAB Deals API v1.0 (comment version)	IAB Tech Lab, 4 Dec 2025
Pass an audience to the auction	Bid request extension	Agentic Audiences v1.1, "integrated with OpenRTB and Prebid"	IAB Tech Lab standards page
Enrich a bid request inside the exchange	Containers hosted by the exchange or DSP	ARTF v1.0 over gRPC with OpenRTB 2.6 protobuf	ARTF repository
Shape bid request traffic	SSP-side filtering on buyer signals	Dynamic Traffic Engine	DTE repository

Agree a private marketplace deal

Where it executes: OpenRTB bid requests that carry the deal
Field or object: imp.pmp.deals[].id, deal floor, allowed seats
Source: OpenRTB 2.6

Book programmatic guaranteed

Where it executes: OpenRTB deal flagged as guaranteed
Field or object: Deal.guar = 1; the IAB Seller Agent sets it "on the wire" from v2.3.2
Source: seller-agent releases

Book a direct guaranteed order

Where it executes: Seller's order management system
Field or object: OpenDirect 2.1 orders and lines
Source: OpenDirect releases

Sync deal terms to DSPs

Where it executes: SSP to DSP deal sync
Field or object: IAB Deals API v1.0 (comment version)
Source: IAB Tech Lab, 4 Dec 2025

Pass an audience to the auction

Where it executes: Bid request extension
Field or object: Agentic Audiences v1.1, "integrated with OpenRTB and Prebid"
Source: IAB Tech Lab standards page

Enrich a bid request inside the exchange

Where it executes: Containers hosted by the exchange or DSP
Field or object: ARTF v1.0 over gRPC with OpenRTB 2.6 protobuf
Source: ARTF repository

Shape bid request traffic

Where it executes: SSP-side filtering on buyer signals
Field or object: Dynamic Traffic Engine
Source: DTE repository

Download JSON

Table by AdSovereign, CC BY 4.0.

So an agent-ready seller is mostly a well-run programmatic seller with an API in front. If your deal IDs are clean, your programmatic guaranteed flow works and your OpenDirect or order API is documented, an agent has rails to land on. The deal types are compared in programmatic guaranteed vs PMP, and the bid request fields in OpenRTB 2.6 explained.

Shipped standards versus proposals

The vocabulary moves fast, so it helps to separate what you can build on from what may change. Status is as of the last update, with sources in the checklist above.

Shipped (a published version exists):

Execution standards: OpenRTB 2.6-202606, AdCOM 1.0 and OpenDirect 2.1.
IAB agent work: AAMP 2.3 reference Buyer and Seller Agents, the Agentic Real-Time Framework (ARTF) v1.0 tag and Agentic Audiences v1.1.
Agent protocols: MCP 2026-07-28, A2A v1.0 and AdCP 3.2 (current tag 3.2.9).
Registries: IAB Tech Lab and AgenticAdvertising.org.

Proposals (draft, in comment or planned):

AAMP 3.0 and OpenProposal, in comment to 10 November 2026 (IAB Tech Lab).
The final IAB Deals API v1.0, which we could not confirm.
"ads.txt for agents", still a roadmap item.
AdCP 4.0 with mandatory request signing for spend, targeted for early 2027 (AdCP versioning).

Only partly covered: agent behaviour. AgenticAdvertising.org's "AAO Verified" mark tests protocol conformance with canonical test campaigns, and IAB Tech Lab reviews registry entries (AdCP, trust and security). Neither certifies how an agent spends a budget. The data risks of connecting outside agents are covered in AI agents and data leakage.

FAQ

What is AAMP at IAB Tech Lab?

AAMP, the Agentic Advertising Management Protocols, is IAB Tech Lab's umbrella programme for AI agents in advertising. It extends existing standards such as OpenRTB, OpenDirect, AdCOM and the Deals API and adds reference Buyer and Seller Agents and a registry. Version 2.3 shipped on 30 July 2026, and 3.0 with OpenProposal is in public comment until 10 November 2026 (IAB Tech Lab, 22 September 2026).

What does agent-ready mean for a publisher?

It means an agent can read your products and deals as data and reach you through an MCP or A2A endpoint. It can confirm you are who you say, then book through an authenticated API with limits and logs. Most of the work is cleaning up catalogue, deal and order data you already have, as the checklist above shows.

Do I need both MCP and A2A?

Not today. Of the 53 entries in the IAB Tech Lab registry on 9 November 2026, 52 used MCP (IAB Tech Lab registry). Start with an MCP server and add an A2A agent card if your partners ask for agent-to-agent delegation.

How do agents avoid inventing prices?

By refusing to act on a price without a source. AAMP 2.3 added a pricing provenance field after IAB Tech Lab flagged "CPM hallucination", and its Seller Agent now requires a real floor price before it creates a deal (PPC Land, 30 July 2026). Your platform should enforce the same rule on its side.

What is Agentic Advertising Connect?

It is a series of community meetups run by AgenticAdvertising.org, the body that publishes AdCP. The first Australian session took place in Sydney on 22 October 2026, with an introduction by founding members and a live demo (AllAI Events listing). A Singapore edition was billed as the first in Asia (Luma listing).

How this works on owned infrastructure

Rows 10 to 15 of the checklist are about control: who may call, how much they may spend, which prices count as real and where the record lives. Those are properties of the system the agent calls, not of the agent. AdSovereign is an enterprise RTB stack (DSP, SSP, exchange, DMP and clean room) designed to run in your own environment, so the tool endpoint, the spend limits, the approval thresholds and the audit log sit on infrastructure you operate. Your own security team then sets the credential scopes and keeps the logs. The integrations page lists supported protocols, and the security page describes the access controls.

Sources

IAB Tech Lab, "IAB Tech Lab Releases AAMP 2.3, Bringing Enterprise-Grade Infrastructure and Privacy Diligence to Agentic Advertising" (30 July 2026). https://iabtechlab.com/press-releases/iab-tech-lab-releases-aamp-2-3-bringing-enterprise-grade-infrastructure-and-privacy-diligence-to-agentic-advertising/
PPC Land, "AAMP 2.3 blocks AI agents from inventing ad prices, IAB Tech Lab says" (30 July 2026). https://ppc.land/aamp-2-3-blocks-ai-agents-from-inventing-ad-prices-iab-tech-lab-says/
IAB Tech Lab, "IAB Tech Lab Introduces AAMP 3.0 to Standardize the RFP-to-Buy Process for Agentic Advertising" (22 September 2026; comment period extended to 10 November 2026). https://iabtechlab.com/press-releases/iab-tech-lab-introduces-aamp-3-0-with-openproposal/
PPC Land, "OpenProposal" explainer (25 October 2026). https://ppc.land/openproposal/
IAB Tech Lab, "Agentic Advertising and AI" standards page (accessed 9 November 2026). https://iabtechlab.com/standards/agentic-advertising-and-ai/
IAB Tech Lab, "Introducing the IAB Tech Lab Agent Registry" (4 March 2026). https://iabtechlab.com/introducing-the-iab-tech-lab-agent-registry/ 6a. IAB Tech Lab, "Navigating the Agentic Frontier: the IAB Tech Lab 2026 roadmap" (letter, April 2026; registry live 3 March 2026). https://iabtechlab.com/navigating-the-agentic-frontier-the-iab-tech-lab-2026-roadmap/
IAB Tech Lab, Agent & MCP Server Registry (read 9 November 2026). https://registry.iabtechlab.ai/
AgenticAdvertising.org, registry statistics endpoint (read 9 November 2026). https://agenticadvertising.org/api/registry/stats
IAB Tech Lab, "IAB Tech Lab Releases Deals API to Standardize Programmatic Deal Sync" (4 December 2025). https://iabtechlab.com/press-releases/iab-tech-lab-releases-deals-api-to-standardize-programmatic-deal-sync/
IABTechLab, seller-agent releases v2.0 to v2.4.2 (8 July to 18 August 2026). https://github.com/IABTechLab/seller-agent/releases

More sources (17)

IABTechLab, agentic-real-time-framework (ARTF) repository and v1.0 release (20 July 2026). https://github.com/IABTechLab/agentic-real-time-framework
IABTechLab, Dynamic Traffic Engine repository (accessed 9 November 2026). https://github.com/IABTechLab/DynamicTrafficEngine
InteractiveAdvertisingBureau, OpenDirect releases, OpenDirect 2.1 (8 July 2024). https://github.com/InteractiveAdvertisingBureau/OpenDirect/releases
InteractiveAdvertisingBureau, openrtb2.x releases, 2.6-202606 (11 June 2026), and OpenRTB 2.6 specification. https://github.com/InteractiveAdvertisingBureau/openrtb2.x/releases
InteractiveAdvertisingBureau, AdCOM specification repository (accessed 9 November 2026). https://github.com/InteractiveAdvertisingBureau/AdCOM
Model Context Protocol, specification releases, revision 2026-07-28 (28 July 2026). https://github.com/modelcontextprotocol/modelcontextprotocol/releases
Model Context Protocol, "Authorization", specification revision 2026-07-28 (accessed 9 November 2026). https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization
A2A Project, releases v1.0.0 (12 March 2026) and v1.0.1 (28 May 2026), and specification. https://github.com/a2aproject/A2A/releases
AdCP documentation 3.2.8, "Authentication" (accessed 9 November 2026). https://docs.adcontextprotocol.org/dist/docs/3.2.8/building/by-layer/L2/authentication.md
AdCP documentation 3.2.8, "Calling an AdCP agent" (idempotency) (accessed 9 November 2026). https://docs.adcontextprotocol.org/dist/docs/3.2.8/protocol/calling-an-agent.md
AdCP documentation 3.2.8, "Trust & Security" (accessed 9 November 2026). https://docs.adcontextprotocol.org/dist/docs/3.2.8/trust.md
AdCP documentation 3.2.8, "Seller verification" (accessed 9 November 2026). https://docs.adcontextprotocol.org/dist/docs/3.2.8/verification/overview.md
AdCP documentation 3.2.8, "Versioning & Governance" (accessed 9 November 2026). https://docs.adcontextprotocol.org/dist/docs/3.2.8/reference/versioning.md
adcontextprotocol/adcp, GitHub releases, v3.2.9 (9 November 2026). https://github.com/adcontextprotocol/adcp/releases
PPC Land, "PubMatic guardrails block AI agents from unapproved ad inventory" (5 August 2026). https://ppc.land/pubmatic-guardrails-block-ai-agents-from-unapproved-ad-inventory/
AllAI Events, "Agentic Advertising Connect - Australia" listing (event on 22 October 2026). https://allai.events/event/agentic-advertising-connect---australia
Luma, "Agentic Advertising Connect - Singapore" listing (accessed 9 November 2026). https://luma.com/sjrmg8y9

Changelog

9 November 2026. First edition. Checklist of 16 capabilities; AAMP 3.0 comment deadline 10 November 2026; AdCP 3.2.9; registry counts 53 (IAB Tech Lab) and 35 enrolled (AgenticAdvertising.org). Next review 9 December 2026.

Author: Art Kukharenko, CEO, AdSovereign. Published: 10 November 2026. Last updated: 10 November 2026.

Key facts

Definition

What agentic AI in programmatic advertising asks of a platform

The agent-readiness checklist

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

Machine-readable inventory and deal descriptions

Endpoints: MCP, A2A and discovery files

Registration: being findable and checkable

Authentication: who is calling, and may they spend?

Guardrails: budget caps, approvals and pricing data integrity

allowed_tools, read_only_tools

spend_limits

human_approval

pricing_rules

idempotency

audit_log

Audit logs: proving what the agent did

How agent workflows map onto OpenRTB and OpenDirect

Agree a private marketplace deal

Book programmatic guaranteed

Book a direct guaranteed order

Sync deal terms to DSPs

Pass an audience to the auction

Enrich a bid request inside the exchange

Shape bid request traffic

Shipped standards versus proposals

FAQ

How this works on owned infrastructure

Sources

`allowed_tools`, `read_only_tools`

`spend_limits`

`human_approval`

`pricing_rules`

`idempotency`

`audit_log`