🎉 AdCP 3.0 is now GA — see what's new
Documentation
- Introduction
- Quickstart
- FAQ
- AI Disclosure
- Trust & Security
curl --request DELETE \
--url https://agenticadvertising.org/api/me/agents/{url} \
--header 'Authorization: Bearer <token>'{
"error": "<string>"
}Remove an agent
Remove one registered agent identified by its url.
A currently-public agent is reflected in the published brand.json manifest. To prevent the registry catalog and brand.json from silently disagreeing, this endpoint returns 409 unpublish_first when the agent is public — PATCH /api/me/agents/{url} with visibility: "private" first (or call DELETE /api/me/member-profile/agents/{index}/publish to reconcile the manifest), then re-issue the DELETE.
curl --request DELETE \
--url https://agenticadvertising.org/api/me/agents/{url} \
--header 'Authorization: Bearer <token>'{
"error": "<string>"
}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.
Authorizations
Bearer token in the Authorization header. Two token types are accepted:
- Organization API key (
sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use. - User JWT obtained via the OAuth 2.1 authorization code flow with PKCE. User-scoped, short-lived. Discover the authorization server at
/.well-known/oauth-authorization-serverand the protected-resource metadata at/.well-known/oauth-protected-resource/api.
Path Parameters
The agent's url, URL-encoded (e.g. https%3A%2F%2Fagent.example.com%2Fmcp).
Query Parameters
WorkOS organization id to act on. Defaults to the caller's primary organization. Use this from a multi-org session (or when shelling with a user JWT) to target a non-primary org. Verification goes through WorkOS membership lookup; non-members get 403.
"org_01HXZAB123"
Response
Agent removed.
Was this page helpful?