FruxonDocs
AgentsCore

Deactivates an agent

Flips the agent's `Enabled` flag to false. New invocations through connectors, schedules, or the gateway are rejected, but already-running executions continue to completion and historical data (executions, traces, evaluations) remains queryable. Configuration and revisions are preserved; re-enable with `POST /v1/tenants/{tenant}/agents/{agent}:activate`. Idempotent.

POST
/v1/tenants/{tenant}/agents/{agent}:deactivate

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

agent*string

The unique identifier of the agent to deactivate.

tenant*string

The tenant identifier

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string:deactivate"
{
  "id": "string",
  "displayName": "string",
  "description": "string",
  "avatarFileId": "string",
  "tags": [
    "string"
  ],
  "type": "SUMMARIZATION",
  "enabled": false,
  "currentRevision": 0,
  "createdAt": 0,
  "modifiedAt": 0,
  "tenantId": "00000000-0000-0000-0000-000000000000",
  "solutionId": "string",
  "deletedAt": 0,
  "evaluationMetrics": [
    {
      "metricId": "00000000-0000-0000-0000-000000000000",
      "weight": 0
    }
  ],
  "origin": "NATIVE",
  "externalConfig": {
    "parameters": {}
  },
  "redactLlmMessages": false
}
Empty
{
  "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
}

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.

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.