Skip to main content

AI ad networks

AI ad networks sit between buyer agents and AI platforms, aggregating inventory across multiple platforms into a single seller interface. The protocol supports this topology natively — an ad network is a seller agent that represents multiple publisher properties it doesn’t own.

How a network appears

To buyer agents, the network is a standard seller agent. Buyers connect to the network’s MCP server, push catalogs and data in via standard tasks, and execute buys. To the underlying AI platforms, the network is an operator — it holds accounts on each platform and forwards the buyer’s catalog data, brand identity, and content standards.

Product modeling for networks

A network’s products can span multiple AI platforms using publisher_properties:
The network decides which platform serves each impression based on context, relevance, and performance. The buyer doesn’t need to know which platform was selected — they see unified delivery reporting from the network.

Account model for networks

Networks typically use implicit accounts (require_operator_auth: false). The buyer agent is trusted and declares brands via sync_accounts. The network then manages its own accounts with each underlying AI platform:
Declare capabilities accordingly:

Catalog forwarding

Networks receive catalogs from buyers via sync_catalogs and forward them to the relevant AI platforms. The same task works on both legs — the network acts as a buyer when syncing catalogs to each platform. This is the core data pipe: brand catalog data flows from buyer → network → platform, giving each platform the raw material to generate ads.

Governance and content standards

Networks can enforce governance policies at the routing layer before forwarding to platforms. When a buyer pushes content standards, the network applies them when selecting which platforms and contexts are eligible — then forwards the policies to each platform so they’re also enforced at creative generation time. This gives brands two layers of suitability enforcement: the network’s routing decisions and the platform’s generation constraints.

Delivery reporting

Networks aggregate delivery data from underlying platforms and present unified reporting to buyers via get_media_buy_delivery. The buyer sees a single delivery report per media buy — the network handles the per-platform breakdown internally. Networks that want to offer platform-level transparency can use reporting_dimensions to expose placement-level breakdowns.

adagents.json for networks

A network’s adagents.json lists the publisher properties it represents, even though it doesn’t own them:
Each underlying AI platform authorizes the network in its own adagents.json. Buyer agents discover the network through the platforms’ authorization chains. When an ad network sells Sponsored Intelligence on behalf of brands, it acts as an intermediary in the SI session flow. The brand syncs offerings to the network via sync_catalogs with type: "offering", and the network forwards them to underlying platforms. When a platform triggers a session, the network routes it to the correct brand agent.
The key fields at each leg: The network handles attribution correlation across the two legs. It knows which platform triggered the session (placement), which media buy funded it (media_buy_id), and which brand responded (offering_id). This lets the network provide unified delivery reporting to buyers via get_media_buy_delivery while each brand agent only sees its own sessions. Networks should forward identity and supported_capabilities unchanged — the brand agent needs accurate host capabilities to negotiate modalities, and the user’s consent was granted for the brand, not the network.
For the SI session lifecycle and capability negotiation details, see the SI overview and implementing SI hosts.