🚀 AdCP 3.1 beta is now available — see what's new
curl --request POST \
--url https://agenticadvertising.org/api/brands/save \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"domain": "acmecorp.com",
"brand_name": "Acme Corp",
"brand_manifest": {}
}
'{
"message": "<string>",
"domain": "<string>",
"id": "<string>",
"revision_number": 123
}Save or update a brand in the registry. Requires authentication. For existing brands, creates a revision-tracked edit. For new brands, creates the brand directly. Cannot edit authoritative brands managed via brand.json.
curl --request POST \
--url https://agenticadvertising.org/api/brands/save \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"domain": "acmecorp.com",
"brand_name": "Acme Corp",
"brand_manifest": {}
}
'{
"message": "<string>",
"domain": "<string>",
"id": "<string>",
"revision_number": 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.Was this page helpful?