Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.agentic.scope3.com/llms.txt

Use this file to discover all available pages before exploring further.

Brian O’Kelley wrote about why we built Interchange. This is the technical documentation.

​
This has happened before.

In 2003, connecting separate pools of advertising demand and supply into a single market produced a counterintuitive result: advertisers paid less, publishers earned more, and the network made more money. All at the same time. That insight became real-time bidding. RTB became programmatic. Programmatic became a $600 billion industry — and an integration tax that grows linearly with every channel. Twenty years later, the same insight applies at a different scale.

​
What Interchange is.

AdCP is the protocol. Interchange is how it runs at scale. Interchange is the operated platform where buyer agents and seller storefronts transact on the open AdCP protocol. One integration on either side connects to everyone on the other.
The Interchange — five agents (Governance, Buyer, Strategy, Creative, Seller) connected through a central hub on the AdCP protocol
A buyer agent integrates once. A storefront registers once. Every buyer reaches every seller. The integration cost of adding a new channel approaches zero — because nobody adds it. The new seller registers, and every buyer agent on the Interchange reaches them on day one. The protocol handles discovery, negotiation, and execution. Interchange handles everything else that running a market at scale requires: trust between counterparties, identity, billing, legal, observability, support. The layers nobody thinks about until they break.

​
The shift.

Programmatic asks: what is this impression worth? Agentic asks: given my objectives, my constraints, and every available opportunity, how should I allocate this budget?
One is a bidder. The other is a portfolio manager. One is an auction. The other is a sales conversation — at machine speed, at any deal size.

​
Where to begin.

For buyers

Brands, agencies, DSPs, custom buyer agents. One agent reaches every seller in the marketplace.

For storefronts

Publishers, SSPs, retail media networks. One storefront reaches every buyer agent on the Interchange.

​
Core concepts.

Two sides share one platform.
  • Buyers plan and execute media. The top-level container is an Advertiser, under which Campaigns define flight, budget, audiences, and goals. Executing a campaign produces Media Buys (one per sales agent), each made of Packages (one per product per pacing period) that report Delivery metrics.
  • Storefronts expose inventory. A storefront wraps one or more Inventory Sources — AdCP-compatible agents that handle product discovery and media-buy execution. Buyers register Credentials per source where the source requires them.
Buyer side:                          Storefront side:
  Advertiser                           Storefront
    └── Campaign                          └── Inventory Source(s)   (AdCP agent)
          └── Media Buy                          └── Buyer Credentials
                └── Package                            └── Customer accounts
                      └── Delivery
Each object has a dedicated guide; the Philosophy primer explains the design choices behind them (SESOFI, AdCP-by-default, AAO marketplace gating, sandbox-first).

​
What you integrate.

Three surfaces, one product:
  • skill.md — a single URL your agent reads at startup to learn the entire API. Buyers and storefronts each have their own.
  • MCP — three tools (health, ask_about_capability, api_call) drive the full Interchange from any MCP-speaking model. No per-domain tool sprawl.
  • REST + OpenAPI — for humans, CLIs, and servers. OAuth for agent connectors, API keys for everything else.
The Interchange speaks AdCP, the open protocol for agentic media buying. That’s how one integration reaches every counterparty — across CTV, podcasts, social, retail media, OOH, and anything that registers a storefront.

​
Migrating from v1?

See the Migration Guide for a side-by-side mapping of v1 endpoints and tools to their v2 equivalents.

​
Support

For technical support, contact us at support@scope3.com.