🎉 AdCP 3.0 is now GA — see what's new
curl --request GET \
--url https://agenticadvertising.org/api/registry/authorizations \
--header 'Authorization: Bearer <token>'{
"agent_url": "<string>",
"evidence": [
"<string>"
],
"rows": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"agent_url": "<string>",
"agent_url_canonical": "<string>",
"property_rid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"property_id_slug": "<string>",
"publisher_domain": "<string>",
"authorized_for": "<string>",
"evidence": "<string>",
"disputed": true,
"created_by": "<string>",
"expires_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z",
"updated_at": "2023-11-07T05:31:56Z",
"override_applied": true,
"override_reason": "<string>"
}
],
"count": 123
}Default endpoint for verification consumers (DSPs, sales houses, agencies). Returns the rows where the requested agent appears as agent_url — typically ≤ a few hundred. Pair with /api/registry/feed?entity_type=authorization to tail subsequent changes via the X-Sync-Cursor header.
evidence defaults to adagents_json only. agent_claim is opt-in (?evidence=adagents_json,agent_claim) to prevent buy-side trust misuse — see specs/registry-authorization-model.md.
curl --request GET \
--url https://agenticadvertising.org/api/registry/authorizations \
--header 'Authorization: Bearer <token>'{
"agent_url": "<string>",
"evidence": [
"<string>"
],
"rows": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"agent_url": "<string>",
"agent_url_canonical": "<string>",
"property_rid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"property_id_slug": "<string>",
"publisher_domain": "<string>",
"authorized_for": "<string>",
"evidence": "<string>",
"disputed": true,
"created_by": "<string>",
"expires_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z",
"updated_at": "2023-11-07T05:31:56Z",
"override_applied": true,
"override_reason": "<string>"
}
],
"count": 123
}Documentation Index
Fetch the complete documentation index at: https://docs.adcontextprotocol.org/llms.txt
Use this file to discover all available pages before exploring further.
Bearer token in the Authorization header. Two token types are accepted:
sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use./.well-known/oauth-authorization-server and the protected-resource metadata at /.well-known/oauth-protected-resource/api.Agent URL to look up. Canonicalized server-side (lowercased, trailing slashes trimmed).
effective (default) applies override layer; raw reads base table.
raw, effective Comma-separated evidence allowlist. Defaults to adagents_json.
"adagents_json,agent_claim"
Was this page helpful?