Platform / intermediary track

AdCP platform track (D1-D4): MCP server architecture, supply path verification, agent trust, RTB-to-AdCP migration patterns, and an infrastructure build project.

Platform / intermediary track (D1–D4)

Members only — Requires Basics credential (A1–A3). Four modules, ~105 minutes total.

This track is for people building AdCP infrastructure: ad tech platforms, exchanges, data companies, and anyone connecting the ecosystem. You’ll learn MCP server architecture, supply chain verification, RTB migration, and build working infrastructure in the build project.

Completing this track (plus A1–A3) earns the AdCP practitioner credential.

---

D1: MCP server architecture

~20 min | Prerequisite: A3

Technical deep dive on building an AdCP-compliant MCP server. Transport options (SSE, Streamable HTTP), tool definition patterns, OAuth/authorization flows, and account management.

Reading list

Building with AdCP

Overview of what it takes to build an AdCP integration.

MCP integration guide

The definitive guide: tool calls, response format, available tools, context management.

Authentication

OAuth 2.0 for agent authentication, token management, and operator credentials.

Accounts and agents

How accounts, agents, and principals relate to each other.

Context sessions

Managing context across multi-turn agent interactions.

Schemas and SDKs

JSON Schemas, TypeScript types, and client SDKs for building faster.

Key concepts

• MCP server architecture — exposing AdCP tasks as tools, handling auth, request routing
• Transport options — Streamable HTTP for most cases, SSE for real-time updates
• Capability advertising — get_adcp_capabilities so other agents know what you support
• Account handling — managing incoming sync_accounts from buyers

Start D1 with Addie

“I’d like to start certification module D1.”

---

D2: Supply path, trust, and property governance

~20 min | Prerequisite: D1

Cryptographic signatures for supply chain verification. How platforms validate agent identity, detect fraud, and ensure trust. The relationship between AdCP and ads.cert.

Reading list

Property governance

Identity, authorization, and data enrichment for participants in AdCP.

AdAgents.json

Agent discovery and declaration — verifiable identity for every agent.

Authorized properties

How publishers declare authorized sellers, and how buyers verify them.

Security

Security implementation patterns for AdCP servers.

Accounts and security

Account-level security, principal hierarchies, and access control.

Property specification

The formal specification for property governance.

Campaign governance

Multi-party validation: how platforms implement the governance flow for autonomous transactions.

Campaign governance specification

The full technical specification: sync_plans, check_governance, report_plan_outcome, audit logs.

Policy registry

Community-maintained compliance policies that governance agents resolve and enforce.

Key concepts

• Agent identity verification — domain ownership, cryptographic signatures, organizational registration
• Supply path transparency — full visibility into which agents handled each transaction
• ads.cert relationship — extending cryptographic verification from RTB to agent-to-agent interactions
• Campaign governance architecture — implement three-party validation: sync governance agents via sync_governance, call check_governance before executing, handle all statuses
• Policy registry integration — resolve policies by ID, integrate natural language policy text and exemplars into governance agent evaluation

Start D2 with Addie

“I’d like to start certification module D2.”

---

D3: RTB coexistence and migration

~20 min | Prerequisite: D2

How AdCP coexists with existing programmatic infrastructure. Migration strategies for DSPs, SSPs, and exchanges. Running parallel systems during transition.

Reading list

Trusted Match Protocol

The real-time execution layer: context match, identity match, and cross-publisher activation.

AdCP and OpenRTB

The clearest view of how AdCP campaign workflows connect to impression-time execution.

Async operations

Handling long-running operations — essential for bridging real-time and agentic systems.

Webhooks

Event-driven updates for delivery, status changes, and campaign modifications.

Error handling

Error patterns, retry strategies, and graceful degradation.

Sandbox

Testing your implementation against sandbox agents before going live.

Implementor FAQ

Common questions and answers from teams building AdCP integrations.

Router architecture

Deployment, fan-out, and provider configuration for the TMP Router.

AI mediation

How demand reaches AI assistants through the Trusted Match Protocol.

Key concepts

• Coexistence strategy — run AdCP alongside OpenRTB, gradually migrating workflows
• TMP as the bridge — TMP connects planning-time media buys to serve-time decisions through two structurally separated operations (Context Match and Identity Match). The TMP Router fans out to configured providers in parallel and the publisher joins responses locally. This is how cross-publisher frequency capping, suppression, and suitability work at impression time
• Router deployment and fan-out patterns — how the TMP Router is deployed, provider configuration, and parallel fan-out to multiple match providers
• Platform-specific migration — DSPs wrap bidding logic, SSPs expose inventory, exchanges translate
• Performance benchmarking — compare agentic vs traditional on campaign performance, efficiency, cost

Start D3 with Addie

“I’d like to start certification module D3.”

---

D4: Build project — AdCP infrastructure

~45 min | Prerequisite: D3

Build working AdCP infrastructure using any AI coding assistant (Claude Code, Cursor, Copilot) with the adcp client library. This is the most ambitious build project.

What you’ll build

• MCP server with AdCP tool definitions
• get_adcp_capabilities implementation
• At least 3 AdCP tasks exposed as tools
• OAuth/authentication flow
• Proper error handling with AdCP error codes

Assessment rubric

Dimension	Weight	What Addie evaluates
Specification quality	20%	Can you specify infrastructure in AdCP terms?
Schema compliance	20%	Protocol compliance across all endpoints
Error handling	15%	Proper error handling with recovery types and async
Design rationale	25%	Can you reason about production architecture?
Extension ability	20%	Can you extend the endpoint with new tasks?

Passing threshold: 70%.

Start D4 with Addie

“I’d like to start certification module D4.”

---

What’s next

After completing D1–D4, you’ve earned the AdCP practitioner credential. From here you can pursue specialist modules:

• S1: Media buy — transaction flows, pricing, orchestration
• S2: Creative — asset workflows, format compliance
• S3: Signals — measurement, attribution, optimization
• S4: Governance — brand safety, campaign governance, compliance, policy registry
• S5: Sponsored Intelligence — conversational brand experiences