Skip to main content
syrto_get_usage reports how much Syrto AI usage the signed-in user has spent recently. It costs nothing to call. Consumption is measured in consumption units (CU).

​
Use this tool to

  • Answer “what have I spent?”, “how much has this work cost?”, or “how much usage have I been getting through?”
  • Get a rough sense of how much of the organization’s allowance is left

​
Arguments

This tool takes no arguments.
syrto_get_usage is scoped to a signed-in user. A connection authenticated with an organization API key has no user attached, so the tool is not offered on that connection at all.

​
Returns

​
string
The unit every figure is counted in - consumption units (CU).
​
object | null
Consumption since the top of the previous hour. This is the shortest window the data supports.
​
object | null
Consumption since 00:00 UTC today - a UTC day, not a local one.
​
object | null
Consumption over the last 7 days.
​
object | null
Consumption over the last 30 days.
​
string
Whose consumption these figures are, and their limits.
Beside result:
​
string
How much of the organization’s Syrto AI allowance is left, as the same twenty-step gauge every response carries - see The allowance gauge. Assistants that display MCP Apps draw it as a battery beside the answer, captioned in words such as “Plenty left” or “Running low” rather than with a number. Absent when the allowance is not known, for example on a plan without a usage cap.
The response also carries the other fields every tool returns. On this tool display_title is always Syrto AI, and warning says when usage reporting is not available on the connection. Each window carries:
​
integer
Consumption units spent in that window.
​
string
Start of the window (UTC, inclusive), floored to the hour.
​
string
End of the window (UTC) - the time of the call.

​
How to read the figures

  • Every window is the signed-in user’s own consumption, never the organization’s total. Colleagues and automated integrations consume from the same allowance.
  • These are not a bill, an invoice, or a remaining balance. They are consumption already recorded. For the organization’s usage and allowance, an administrator can open the Syrto dashboard.
  • Very recent calls may not be counted yet. Usage events are buffered, so a call made moments ago may not appear.
  • There is no figure for “this conversation”. The server sees individual tool calls and cannot tell where one piece of work starts or ends; since_hour is the closest available answer.
  • The windows are UTC and floored to the hour, so “today” means since 00:00 UTC, which may not line up with a local day. Each window reports the start it was actually measured from.
  • How much is left is answered only roughly, by the allowance gauge. It describes the organization’s allowance rather than the user’s own spending, and it moves in steps of a twentieth.

​
Example

Response (abbreviated):