概要

​

概要

​

パブリッシャー側: adagents.json

{
  "$schema": "https://adcontextprotocol.org/schemas/v2/adagents.json",
  "properties": [
    {
      "property_id": "example_site",
      "property_type": "website",
      "name": "Example Site",
      "identifiers": [{"type": "domain", "value": "example.com"}]
    }
  ],
  "authorized_agents": [
    {
      "url": "https://agent.example.com",
      "authorized_for": "Official sales agent",
      "authorization_type": "property_ids",
      "property_ids": ["example_site"]
    }
  ],
  "property_features": [
    {
      "url": "https://api.scope3.com",
      "name": "Scope3",
      "features": ["carbon_score", "sustainability_grade"]
    },
    {
      "url": "https://api.onetrust.com",
      "name": "OneTrust",
      "features": ["gdpr_compliant", "tcf_registered"]
    }
  ]
}

​

property_features によるガバナンスエージェント発見

• Sustainability: Scope3 がカーボン排出を計測していると宣言
• Compliance: OneTrust が同意データを管理していると宣言
• Certification: TAG が不正防止を検証したと宣言

​

バイヤー側: プロパティデータと選定

​

プロパティデータプロバイダー

{
  "governance": {
    "property_features": [
      { "feature_id": "consent_quality", "type": "quantitative", "range": { "min": 0, "max": 100 } },
      { "feature_id": "coppa_certified", "type": "binary" },
      { "feature_id": "carbon_score", "type": "quantitative", "range": { "min": 0, "max": 100 } }
    ]
  }
}

• Compliance vendors (data integrity, consent quality)
• Brand safety providers (content classification, risk scoring)
• Quality measurement (viewability, fraud detection)
• Sustainability providers (carbon scoring, green hosting)

​

ガバナンスエージェントによるプロパティ選定

{
  "tool": "create_property_list",
  "arguments": {
    "name": "Q1 Campaign - UK Premium",
    "base_properties": [
      {
        "selection_type": "publisher_tags",
        "publisher_domain": "raptive.com",
        "tags": ["premium_news"]
      }
    ],
    "filters": {
      "countries_all": ["UK"],
      "channels_any": ["display", "video"],
      "feature_requirements": [
        { "feature_id": "consent_quality", "min_value": 85, "max_value": 100 }
      ]
    },
    "brand_manifest": {
      "brand_name": "ToyBrand",
      "industry": "toys",
      "target_audience": "children_under_13"
    }
  }
}

​

全体の流れ

​

完全なフロー

1. Publisher declares properties, sales agents, AND governance agents in adagents.json
2. Buyer discovers governance agents by reading property_features from adagents.json
3. Buyer queries each governance agent’s get_adcp_capabilities for detailed capabilities
4. Buyer creates property lists on each governance agent with filters and brand manifests
5. Governance agents evaluate properties and notify buyer via webhooks when lists change
6. Buyer aggregates results into a final compliant list
7. Buyer shares property list reference with sellers (with auth token)
8. Seller caches resolved list for bid-time decisions

​

セラーとのプロパティリスト共有

1. Get a list reference: The buyer agent exposes the list via get_property_list
2. Issue an auth token: The buyer generates a token that authorizes access to the list
3. Pass to seller: Include property_list_ref with auth_token in product discovery or media buy requests
4. Seller caches locally: Sellers fetch and cache the resolved list for bid-time decisions
5. Webhooks for updates: When the list changes, sellers are notified to refresh their cache

{
  "property_list_ref": {
    "agent_url": "https://buyer-agent.example.com",
    "list_id": "pl_q1_uk_premium",
    "auth_token": "eyJhbGciOiJIUzI1NiIs..."
  }
}

{
  "tool": "get_products",
  "arguments": {
    "brief": "UK video inventory for Q1",
    "property_list_ref": {
      "agent_url": "https://buyer-agent.example.com",
      "list_id": "pl_q1_uk_premium",
      "auth_token": "..."
    }
  }
}

​

Relationship to Other Protocols

​

Property Governance + Media Buy

• Product discovery: Pass property_list_ref to get_products to filter inventory to compliant properties
• Media buy creation: Reference property lists to constrain where ads can run
• Authorization: adagents.json validates agent authority to sell

​

Property Governance + Signals

​

Tasks

​

Discovery

• get_adcp_capabilities: Discover governance capabilities including property features (protocol-level task)

​

Property List Management

• create_property_list: Create a new property list on a governance agent
• get_property_list: Retrieve resolved properties (with caching guidance)
• update_property_list: Modify filters or base properties
• delete_property_list: Remove a property list

​

Getting Started

1. Create /.well-known/adagents.json with property definitions
2. Authorize sales agents for your properties
3. Declare governance agents in property_features (Scope3 for carbon, OneTrust for consent, TAG for certification, etc.)

1. Discover governance agents by reading property_features from publishers’ adagents.json files
2. Query each governance agent’s get_adcp_capabilities for capabilities
3. Create property lists on relevant governance agents with filters and brand manifests
4. Aggregate results into a final compliant list
5. Share property list references with sellers (with auth tokens)

1. Implement get_adcp_capabilities to advertise your capabilities in governance.property_features
2. Implement property list CRUD operations
3. Support webhooks to notify buyers when evaluations change
4. Work with publishers to get listed in their property_features
5. See the Protocol Specification for implementation details