FruxonDocs
AgentsRevisions

Creates a new agent revision.

Creates a draft revision with the specified configuration. The revision is not active until deployed via the deploy endpoint.

POST
/v1/tenants/{tenant}/agents/{agent}/revisions

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.

tenant*string

The tenant identifier

Request Body

The revision configuration.

comment?string|null
definition*

The semantic configuration of a standalone Agent. It intentionally has no graph step type, identifier, name, edge, or boundary-node fields.

parametersMetadata?
integrationSlots?
integrationBindings?
assets?

Assets attached to the revision. Only Fruxon.Model.Agents.AgentAsset.Id is read on write — a draft stores the reference alone; the rest is display metadata the server hydrates on read so a client can name the asset and insert its link.

slots?
[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string/revisions" \  -H "Content-Type: application/json" \  -d '{    "definition": {}  }'
{
  "agentId": "string",
  "revision": 0
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
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
}

Gets the execution parameters for an agent.

Returns the parameters required to execute the agent, including input schema, default values, and validation rules.

Gets the agent revision reliability rollup summed across every environment.

Use `*` as the revision parameter to aggregate across all revisions. Buckets with no executions are omitted from the response — chart clients dense-fill. Relevance (silence) pre-gate records are excluded so they don't skew counts or durations.