Cancels a pending agent deletion within the grace period
Restores an agent that was soft-deleted via `DELETE /v1/tenants/{tenant}/agents/{agent}` but has not yet been purged. The agent reappears in list/get responses with its previous configuration and collaborators intact. Returns 400 if the agent is not currently in a pending-delete state, and 404 if the grace period has already expired and the agent was purged.
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.
The tenant identifier
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string:cancelDelete"{
"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
}Lists all agents the current user has access to.
Tenant admins receive every agent in the tenant; other users receive only the agents on which they have an explicit collaborator role (Viewer, Editor, or Admin). The response is unpaginated and includes soft-deleted agents only while they are still within the deletion grace period. Use this to populate agent pickers; for per-agent detail, follow up with `GET /v1/tenants/{tenant}/agents/{agent}`.
Creates a new agent.
Provisions a new agent shell with an empty draft revision and grants the calling user the Admin role on it. No flow is deployed yet — the agent is not executable until you build a revision via the agent-revisions endpoints and deploy it with `POST /v1/tenants/{tenant}/agents/{agent}/revisions/{revision}:deploy`. Returns 201 with the new agent's ID, which is used in the path of all subsequent agent-scoped calls.