A2: Your first media buy
Free module — No account required. ~20 minutes with Addie. Prerequisite: A1.
Learning objectives
- Execute the full media buy lifecycle: discovery, purchase, creative sync, delivery
- Identify the agent roles involved: buyer agent, sales agent, creative agent, signals agent
- Read and understand real protocol messages at each stage
- Recognize that 3.1 products may describe creative requirements with canonical
format_options[]that narrow sharedformat_kindcontracts - Observe a live agent-to-agent transaction
- Read a capability declaration: some objects signal support by being present, while others carry an explicit
supportedflag that can befalse - Recognize the two things that make agent-to-agent requests safe: the request is signed (so the seller can verify who sent it) and it carries an
idempotency_key(so a retry doesn’t double-book)
Reading list
Protocol architecture
The complete architecture: domain map, identity layer, transaction domains, governance, and ecosystem layers.
MCP integration guide
How MCP works in practice: tool calls, response format, context management, async operations.
Capability discovery
How agents advertise their capabilities so other agents can discover what they offer.
AdAgents.json
Publisher authorization for which agents can sell or enrich inventory.
Seller setup
How sellers use brand.json with adagents.json for identity and supply path verification.
A2A guide
The Agent-to-Agent protocol — how specialized agents collaborate on complex campaigns.
Task lifecycle
How tasks move through states: from request to completion, including async operations.
Key terms
Protocol versioning
Every request carriesadcp_major_version; sellers advertise supported versions on get_adcp_capabilities. A3 and B1 go deeper on version negotiation.
Reading capabilities
get_adcp_capabilities also tells buyers what a seller supports, and each capability follows its own schema contract. Optional feature objects such as media_buy.audience_targeting signal support by being present. Other blocks carry an explicit flag, and some must be declared even when the answer is no: every agent declares adcp.idempotency, with {"supported": false} when it does not deduplicate retried requests. Read each capability the way its schema defines it rather than applying one rule to all of them. B1 goes deeper on how sellers declare capabilities.
What you’ll do with Addie
Tell Addie what you want: audience, goals, budget. Then walk through each step as it happens:- Discovery —
get_productsagainst@cptestagent, examine real response structure - Purchase —
create_media_buywith targeting and budget. Addie points out two things on this request: it carries a signature (so the seller can verify the buyer) and anidempotency_key(so a retry after a network error never creates two buys). Note theconfirmed_attimestamp in the response — this is the seller’s order confirmation. - Creative —
sync_creativesto deliver assets to the publisher - Status check —
get_media_buysto see lifecycle state, creative approvals, andvalid_actions - Delivery —
get_media_buy_deliveryto see results
Assessment
Passing threshold: 70%.
Start this module
Start A2 with Addie
Open Addie and say “I’d like to start certification module A2.”