Skip to main content

AdCP Ecosystem Reference

Token-efficient reference for understanding AdCP’s organizations, repositories, and component relationships. Designed for both human readers and AI agents.

Organizations

OrganizationPurposeURL
AgenticAdvertising.orgMembership community, working groups, member profilesagenticadvertising.org
AdCP (Ad Context Protocol)Protocol specification, schemas, documentationadcontextprotocol.org
Key distinction: AgenticAdvertising.org is the community. AdCP is the protocol. Members join AgenticAdvertising.org to develop and adopt AdCP.

Repositories

All repos are under the adcontextprotocol GitHub organization.
RepoPurposeKey Contents
adcpProtocol and AgenticAdvertising.orgJSON schemas, TypeScript/Python SDKs, protocol docs, AgenticAdvertising.org server (Addie AI, membership, profiles)
salesagentReference sales agent implementationSales agent code, salesagent docs, deployment configs
creative-agentReference creative agentCreative workflows, standard formats, format validation

Channel-to-Repo Mapping

For Slack channels → GitHub issues:
Channel PatternTarget RepoReason
#salesagent-*salesagentSales agent implementation and docs
#creative-*creative-agentCreative agent and formats
#adcp-dev, #protocol-*adcpCore protocol and schemas
#general, #community, #membershipadcpAgenticAdvertising.org server and community features

SDK Packages

LanguagePackageInstall
JavaScript/TypeScript@adcp/clientnpm install @adcp/client
Pythonadcppip install adcp

Protocol Components

┌─────────────────────────────────────────────────────────────┐
│                     PRINCIPALS                              │
│            (Advertisers, Agencies, Brands)                  │
└─────────────────────┬───────────────────────────────────────┘
                      │ Authenticate via

┌─────────────────────────────────────────────────────────────┐
│                  ORCHESTRATING AGENTS                       │
│         (AI Agents executing media buying tasks)            │
└─────────────────────┬───────────────────────────────────────┘
                      │ AdCP Tasks (MCP/A2A/REST)

┌─────────────────────────────────────────────────────────────┐
│                    SALES AGENTS                             │
│       (Publisher-side agents handling inventory)            │
└─────────────────────┬───────────────────────────────────────┘
                      │ Platform APIs

┌─────────────────────────────────────────────────────────────┐
│                 AD PLATFORMS/SERVERS                        │
│    (Google Ad Manager, TTD, Meta, etc.)                     │
└─────────────────────────────────────────────────────────────┘

Core AdCP Tasks

TaskPurposeCategory
get_productsDiscover inventory via natural languageDiscovery
list_creative_formatsGet supported creative formatsDiscovery
create_media_buyPurchase advertising inventoryExecution
get_media_buyCheck campaign statusExecution
modify_media_buyUpdate running campaignsExecution
sync_creativesUpload/register creative assetsCreative
discover_signalsFind targeting signalsSignals
activate_signalEnable signal for targetingSignals

Reference Agents

AgentURLPurpose
Test Sales Agenthttps://salesagent.adcontextprotocol.orgTesting and examples
Reference Creative Agenthttps://creative.adcontextprotocol.orgStandard creative formats

Schema Locations

  • Base URL: https://adcontextprotocol.org/schemas/v2/
  • Core schemas: /schemas/v2/core/ (product, media-buy, creative, error)
  • Task schemas: /schemas/v2/media-buy/ and /schemas/v2/signals/
  • Enum schemas: /schemas/v2/enums/

This is a placeholder document. Content will be enhanced in future updates.