Deletes an agent
Soft-deletes the agent: it disappears from list/get responses immediately, all running executions are abandoned, and a background purge job removes underlying data (revisions, execution history, traces, collaborator grants) after a grace period. During the grace window the deletion can be reversed with `POST /v1/tenants/{tenant}/agents/{agent}:cancelDelete`; once the purge runs the agent ID is unrecoverable. Returns 204 on success and is idempotent against an already-deleted agent (returns 404).
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The unique identifier of the agent to delete.
The tenant identifier
Response Body
curl -X DELETE "https://api.fruxon.com/v1/tenants/string/agents/string"{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Retrieves a specific agent by ID.
Returns the agent's top-level metadata (name, description, enabled flag, current deployed revision number, deletion state). The response reflects the live deployed configuration, not the draft — use `GET /v1/tenants/{tenant}/agents/{agent}/revisions/{revision}` to inspect a specific revision's flow definition. Returns 404 if the agent does not exist or has been purged after a delete; soft-deleted agents in the grace period are also hidden.
Updates an existing agent
Patches top-level agent metadata (display name, description, etc.). This does not touch the flow definition or any revision — to change the executable behavior, edit the draft revision and redeploy. The update is applied to the live agent record immediately and is visible to all collaborators on the next read. Returns 404 if the agent has been deleted or is still in the deletion grace period from another caller.