Timeseries returns the caller org's LLM usage over time as an evenly-spaced…
Timeseries returns the caller org's LLM usage over time as an evenly-spaced series.
GET /v1/event/timeseries
| Address | https://api.hanzo.ai/v1/event/timeseries |
| Method | GET |
| Operation | get_event_timeseries |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Timeseries returns the caller org's LLM usage over time as an evenly-spaced series. One point per hour or per day — the bucket the window implies, 24h giving hours and 7d/30d giving days — carrying requests, total tokens and spend in cents. Empty buckets are filled with zeros so a client charts a continuous line.
The org is the validated principal's — never a parameter. 403 without a validated bearer, 400 on an unknown range, 503 when the warehouse is unreachable.
Request
3 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
range | query | string | — | Range is a relative window: a count and a unit — 24h, 7d, 90d, any <N>h or <N>d — or day, week, month, all. Default 24h. |
start | query | string | — | Start is the inclusive lower bound of a custom window, RFC3339. |
end | query | string | — | End is the exclusive upper bound of a custom window, RFC3339. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | Timeseries | ok |
200 body — 12 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
end | body | string | — | End is the window's exclusive upper bound, RFC3339 UTC. |
interval | body | string | — | Interval is the bucket width: hour or day. |
range | body | string | — | Range is the window that was actually applied: 24h, 7d, 30d or custom. |
scope | body | Scope | — | |
scope.org | body | string | — | Org is the IAM org slug the rows were read under: the validated principal's, resolved server-side. |
series | body | UsagePoint[] | — | Series is one point per bucket, oldest first, with empty buckets zero-filled. |
series[].requests | body | integer | — | Requests is how many LLM calls fell in this bucket. |
series[].spendCents | body | integer | — | SpendCents is what they cost, in cents. |
series[].t | body | string | — | T is the bucket's start, RFC3339 UTC, aligned to the interval. |
series[].tokens | body | integer | — | Tokens is prompt plus completion tokens over those calls. |
source | body | string | — | Source is the warehouse table the series read. |
start | body | string | — | Start is the window's inclusive lower bound, RFC3339 UTC. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, EventApi } from 'hanzoai';
const api = new EventApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getEventTimeseries();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import EventApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = EventApi(client).get_event_timeseries()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.EventAPI.GetEventTimeseries(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, event_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = event_api::get_event_timeseries(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.EventApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new EventApi(client).getEventTimeseries();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/event/timeseries \
-H "Authorization: Bearer $HANZO_API_KEY"The door declares no tool for event — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?