Skip to main content
The Interchange has two object hierarchies that meet at the AdCP wire. Buyers plan and execute media; storefronts expose inventory. Both sides share one platform and one auth model, but their objects are disjoint — an agent only ever works inside the hierarchy that matches its job. This page is the canonical map. Each side gets an ASCII tree, then a table per object: what it is, its parent, what nests under it, and the guide that covers it.
Media Buys and Packages are not directly creatable. They are spawned by the platform when a Campaign executes — one media buy per sales agent, one package per product per pacing period. You read their status and tune them through the campaign update endpoint, never by POSTing them directly.

Buyer side

A buyer’s world is rooted at the Advertiser and flows down to the Delivery metrics that roll back up. Discovery, creatives, signals, and audiences attach to the Campaign — the focal object.

Storefront side

A storefront’s world is rooted at the Storefront and wraps one or more AdCP-compatible Inventory Sources. Buyers register Credentials per source where the source requires them; those credentials gate the buyer accounts that transact through the storefront.
The two hierarchies meet at the AdCP wire: a buyer’s Media Buy is the same transaction a storefront approves through Media-Buy Approval, and a buyer’s Discovery Session is answered by a storefront’s Proposals. Read the Philosophy primer for why the surfaces are split.

Where to go next

Philosophy

Why v2 splits buyer and storefront, uses SESOFI, and defaults to AdCP.

Glossary

Every term in the docs, alphabetized with links to the deep guides.

Campaign

The focal buyer object — how a plan becomes media buys and packages.

Storefront

Wrap inventory sources, manage credentials, and connect buyer accounts.