Gets the agent revision cost summed across every environment.
Use `*` as the revision parameter to aggregate across all revisions. Cost buckets with no LLM usage are omitted from the response; execution-count buckets are independent and surface failures that occurred before any LLM call.
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
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/costTimeseries"{
"agentId": "string",
"revision": 0,
"interval": "HOUR",
"window": {
"fromMs": 0,
"toMs": 0
},
"cost": [
{
"bucketStartMs": 0,
"cost": {
"input": 0,
"output": 0,
"total": 0
},
"tokens": {
"input": 0,
"output": 0
}
}
],
"executions": [
{
"bucketStartMs": 0,
"count": 0
}
]
}{
"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 aggregated cost for a specific agent revision or all revisions.
Returns cost information including total input/output costs, token usage, and execution count. Use `*` as the revision parameter to aggregate costs across all revisions.
Checks whether a deploy or revert would use soft-deleted integration configs.
Call before `:deploy` when reverting to an older revision. A non-empty result means deploying would leave the agent with a severed credential — surface a restore/repoint prompt and resolve it first (the deploy itself rejects with 400 otherwise). Empty for the common case. See `docs/design/integration-config-deletion-lifecycle.md`.