Gets agent revision cost split by environment.
At least one `environment` query parameter is required; repeat the param to compare multiple environments side-by-side (`?environment=production&environment=staging`). Unknown slugs (not present in the tenant's environments table) are rejected with 400 — silent-empty would mask FE typos that drift from real config.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
Agent identifier.
Revision number, or * for all revisions.
The tenant identifier
Query Parameters
One or more environment slugs to compare.
Bucket granularity (hour, day, week). Defaults to day.
"UNSPECIFIED" | "HOUR" | "DAY" | "WEEK"Window start as Unix milliseconds (inclusive). Defaults to 30 days before to.
int64Window end as Unix milliseconds (exclusive). Defaults to now.
int64Execution origin to roll up. Defaults to PRODUCTION. Pass
TEST for developer test spend.
"UNSPECIFIED" | "PRODUCTION" | "TEST"Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/revisions/string/environmentCostTimeseries"{
"agentId": "string",
"revision": 0,
"interval": "HOUR",
"window": {
"fromMs": 0,
"toMs": 0
},
"environments": [
{
"slug": "string",
"cost": [],
"executions": []
}
]
}{
"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
}Returns the deploy audit history for an agent.
Each row records a deploy attempt (successful or failed), the previous and target revision, the user who triggered it, the per-connector activation results, and the time of the deploy. Rows are ordered newest first.
Retrieves a specific agent revision.
Returns the immutable snapshot of an agent's configuration at the given revision number, including the flow graph (nodes, edges, prompts, tool bindings), the input parameter schema, and the revision's deployment status. The revision identifier may be a numeric version, or pass `draft` to inspect the in-progress unsaved revision being edited. Deployed revisions are read-only; use the create-agent-revisions endpoints to fork a new draft and deploy it with `POST .../revisions/{revision}:deploy`.