Stop using a registry skill — remove the linked pointer
Remove this org’s Use pointer(s) for a registry skill.
The inverse of POST /use, and deliberately its mirror image in two ways.
Scope-agnostic by default. POST /use writes at a scope, but nobody
removing a skill thinks in scopes — they think “get this off my agents”. So the
default removes every pointer this org holds for the skill, workspace-wide and
per-agent alike. Pass agents to unlink only those names; a workspace-scoped
pointer is untouched by that (it is not any one agent’s, and dropping it would
silently remove the skill from agents the caller did not name).
Idempotent. Removing a skill you no longer have is 200 with removed: 0,
matching the way /use upserts rather than 409-ing on a second call. A remove
control that errors the second time it is pressed is a worse UI than one that
does nothing, and retries after a dropped response are the common case.
A fork is untouched — that is an owned skill in your org, deleted through the skills API. This route only cuts links.
Authorizations
Enter your API key (e.g. dai_sk_test_key_001)
Headers
Path Parameters
Query Parameters
Comma-separated agent names to unlink. Omit to remove every pointer for this skill.
Cookies
Response
Pointer(s) removed. Idempotent: removing nothing is still 200.