---
title: "Per-day spend over a trailing window (compute + inference segments)"
method: GET
path: "/v1/orgs/{orgId}/usage/daily"
tags: ["Usage"]
---

# Per-day spend over a trailing window (compute + inference segments)

`GET /v1/orgs/{orgId}/usage/daily`

Display aggregation for the dashboard spend chart. Buckets the org's usage-record cost (clamped per UTC day) and drained inference debits by calendar day, with per-product segments. Read-only: rides the same pricing iterator as settlement and the deploy gate, never re-prices.

## Path parameters

- `orgId` string, required

## Query parameters

- `days` integer

## Response `200`

OK

- DailyUsage
  - `daily` DailyUsagePoint[], required — one point per day, oldest first, zero-filled so the series is continuous
    - `cents` integer, required — total spend attributed to this day
    - `date` string, required — UTC calendar day, YYYY-MM-DD
    - `segments` UsageSegment[], required
      - `cents` integer, required
      - `key` string, required — display segment: a GPU model name, "CPU", or "Inference"
  - `previousCents` integer, required — total spend in the same-length window immediately before this one
  - `previousSegments` UsageSegment[], required
    - `cents` integer, required
    - `key` string, required — display segment: a GPU model name, "CPU", or "Inference"

## Other responses

- `400` — The request is invalid
- `401` — Missing or invalid API key
- `403` — API key lacks the required scope

---

[API](https://skmtc.net/openrelay/apis/openrelay-api.md) · [All operations](https://skmtc.net/openrelay/apis/openrelay-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/openrelay/openrelay-api/versions/4c42fd61ed41/schema)