🔗 AdAgents.json Manager
Validate, create, and manage adagents.json files for the Ad Context Protocol. Ensure your domain properly declares authorized sales agents according to the AdCP specification.
Manage Your AdAgents.json
Enter your domain to validate, view, or edit your adagents.json file. If you don't have one yet, we'll help you create it.
📍 adagents.json for
No file found • Creating new
Enter the HTTPS URL where the authoritative adagents.json file is hosted
Third-party certification agents (e.g., Scope3, TAG, OneTrust) that provide property-level data. Buyers use these to discover which certification agents cover your inventory.
Add feature provider
Recurring content programs (shows, newsletters, event series) whose inventory is sold through authorized agents.
Add collection
Canonical ad placements for properties in this file. Buyers can scope authorization to specific placement IDs or tags.
Add placement
Placement tags
Named tags for grouping placements. Agents can be authorized by placement tag in the Agents tab.
Edit Property
Edit Agent
Commercial relationship: direct (your sales path), delegated (agent manages your monetization), ad_network (sold through network/package)
When checked, other agents in this file are NOT authorized for the same scoped inventory.
Restrict this authorization to specific countries. Two-letter country codes, e.g. US, CA.
Each key: enter the JWK kid (≤8 chars) and base64url-encoded X25519 public key (x, 43–44 chars).
Paste each key as a JWK JSON object (Ed25519, P-256, or RSA public key).
Restrict this agent to placements defined in the Placements tab. Leave unchecked for no placement restriction.
Import from registry
Edit Signal
📚 Need Help?
Learn more about the AdCP specification and adagents.json format:
AdCP Specification Details
The adagents.json file must be hosted at /.well-known/adagents.json and follow the AdCP
specification:
Required Structure (AdCP v2.2.0):
{
"$schema": "https://adcontextprotocol.org/schemas/latest/adagents.json",
"authorized_agents": [
{
"url": "https://agent.example.com",
"authorized_for": "Description of authorization scope",
"delegation_type": "direct",
"property_ids": ["website_main", "ctv_app"]
}
],
"properties": [
{
"property_id": "website_main",
"property_type": "website",
"name": "Main Website",
"identifiers": [
{ "type": "domain", "value": "example.com" }
],
"tags": ["premium"]
}
],
"last_updated": "2025-01-10T12:00:00Z"
}
Key Requirements:
- HTTPS Required: All agent URLs must use HTTPS
- Authorization Scope: 1-500 characters describing what each agent is authorized to do
- Property IDs (Optional): List specific properties each agent can sell. If omitted, agent can sell all properties.
- Properties Array (Optional): Declare your digital inventory (websites, apps, etc.) with unique identifiers
- Domain Matching: Agents validate authorization based on publisher domain
- Agent Cards: Each agent should provide a valid agent card at their endpoint
Note: This tool validates against the AdCP adagents.json specification. The structure and requirements shown above reflect the current protocol standards.