Delete an agent
DELETE/v1/projects/:project_id/agents/:agent_id
Deletes an agent by ID. Fails with 409 if the agent has dependent generations or traces, or another project has accepted a share of it, unless force=true is passed, in which case those generations and traces are deleted along with the agent and the shares are revoked. Every share of the agent is revoked when it is deleted.
Request
Responses
- 204
- 400
- 401
- 403
- 404
- 409
- 429
- 500
- 502
- 4XX
Deleted
The request was malformed or failed validation.
Unauthorized
Forbidden
Not found
Agent has dependent generations, traces, accepted shares or ingestion rules in its own project (pass force=true to delete anyway; records and rules another project made through a share are kept). error.meta carries generation_count, trace_count, accepted_share_count and ingestion_rule_count so a caller can tell which one is nonzero.
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there