FruxonDocs
Agent NetworkTriggers

What the automation spent in the current budget window, agent by agent.

Every agent the automation spends through, not only the ones its stages run per item: a question held as a conversation spends through the agent that holds it — its opening turn, every reply, the notices it posts and the outcome it tells — and none of those runs is named by a transition, so the funnel and the item costs cannot see them. Each agent's spend is split into what it was for. The window is the agents' own budget window (UTC, calendar-aligned), so a row here and that agent's limit are measured over the same span. An agent that also works elsewhere — chat, another automation — spends more against its limit than it spent here; that difference is the reason to read the two together. Production runs only; refused runs cost nothing and are not counted.

GET
/v1/tenants/{tenant}/triggers/{trigger}/ledger/spend
AuthorizationBearer <token>

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

In: header

Path Parameters

trigger*string

The trigger identifier.

Formatuuid
tenant*string

The tenant identifier

Query Parameters

period?string

The window: DAILY, WEEKLY (default) or MONTHLY.

Default"WEEKLY"
Value in"UNSPECIFIED" | "DAILY" | "WEEKLY" | "MONTHLY"

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/spend"
{
  "period": "DAILY",
  "from": 0,
  "to": 0,
  "cost": 0,
  "credits": 0,
  "runs": 0,
  "agents": [
    {
      "agentId": "string",
      "cost": 0,
      "credits": 0,
      "runs": 0,
      "parts": []
    }
  ]
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}