Skip to main content

Required tasks by protocol

Each AdCP protocol defines tasks that agents implement depending on their role. This page consolidates the requirements from each protocol specification into a single reference. Legend: Required — the specification mandates implementation. Conditional — required when the agent has a specific capability. Optional — the specification recommends but does not mandate. Some tasks span protocols. For example, list_creative_formats and sync_creatives are defined in the Creative Protocol but also implemented by Media Buy sales agents. These appear under both protocols with a note indicating the source.

Shared

Every AdCP agent, regardless of protocol, implements: Caller-scope RBAC introspection is not a standalone task. Sellers that support scope introspection return a per-account authorization object on sync_accounts and list_accounts responses. See Accounts Protocol — Caller authorization. AdCP task lifecycle state is application-layer state, not MCP-native or A2A-native task state. 3.x sellers MAY advertise non-colliding AdCP aliases for polling and reconciliation: get_task_status for legacy tasks/get, and list_tasks for legacy tasks/list. These aliases are optional compatibility surfaces in 3.x; callers MUST continue to support the legacy names through the 3.x line.

Media Buy Protocol

Sales agent (seller)

Sales agents MUST also support at least one transport (MCP or A2A) and declare media_buy in supported_protocols. Reference: Media Buy Specification · Seller integration guide

Orchestrator (buyer)

Orchestrators are not MCP/A2A servers — they call sales agent tasks. Conformant orchestrators MUST:
  1. Authenticate with sales agents
  2. Include required fields per request schemas
  3. Handle asynchronous task-level responses (submitted, working, input-required) and webhook delivery of completion artifacts
  4. Use media_buy_id for all subsequent operations
  5. Respect creative_deadline for creative uploads
Reference: Media Buy Specification — Orchestrator conformance

Creative Protocol

Creative agent

Creative agents MUST return authoritative format definitions only for formats they own. Reference: Creative Specification

Signals Protocol

Signal agent

Signal agents MUST enforce access control for private signals and activation keys. Reference: Signals Specification

Brand Protocol

Brand agent

Brand agents MUST declare brand in supported_protocols. Reference: Brand Protocol · Building a brand agent

Accounts Protocol

Any agent accepting accounts

Agents MUST implement at least one of sync_accounts or list_accounts depending on their account model. An agent MAY implement both (e.g., ad networks that use buyer-declared accounts on the buyer side and account-id namespaces with underlying platforms). Reference: Accounts Protocol

Governance: Campaign

Governance agent

Reference: Campaign Governance Specification

Governance: Property

Governance agent

Reference: Property Governance Specification

Governance: Collection

Governance agent

Reference: Collection Governance

Governance: Content Standards

Content standards agent

Reference: Content Standards

Governance: Creative

Creative governance agent

Reference: Creative Governance

Brand agent

Brand agents MUST declare sponsored_intelligence in supported_protocols. Reference: Sponsored Intelligence Specification

Trusted Match Protocol

TMP uses a different communication model (direct HTTP, not MCP/A2A tasks). See the TMP Specification for message types and conformance requirements.