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.
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 GET "https://api.fruxon.com/v1/tenants/string/agents/string"{
"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
}{
"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
}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.
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).