Console

Usage & billing

See exactly what you are consuming and what it costs, from the whole organization down to a single key.

Where to look

Total usage — organization-wide spend and volume, with a daily time series and a breakdown by project and by user.
Inference API → Usage — usage for the selected project and per individual key.
Events — the underlying line items, each request with its model, tokens and cost.

Reading it programmatically

The same numbers are available from the API. Aggregate cost for an organization:

Organization usage

curl "https://api.upgreat.ai/v1/orgs/{orgId}/usage" \
  -H "Authorization: Bearer <access-token>"

A daily time series, ideal for charts and finance exports:

Daily time series

curl "https://api.upgreat.ai/v1/orgs/{orgId}/usage/daily" \
  -H "Authorization: Bearer <access-token>"

Drill into one project, or one key:

Per-project and per-key

# Aggregated for a project
curl "https://api.upgreat.ai/v1/projects/{projectId}/usage" \
  -H "Authorization: Bearer <access-token>"

# Line items for a project
curl "https://api.upgreat.ai/v1/projects/{projectId}/usage/events" \
  -H "Authorization: Bearer <access-token>"

# Usage and cost for a single inference key
curl "https://api.upgreat.ai/v1/inference/keys/{keyId}/usage" \
  -H "Authorization: Bearer <access-token>"

Pricing per model

The models available to an organization, with their pricing, come from GET /v1/orgs/{orgId}/models. Combine that with usage events to reconcile spend down to the request.

Cost attribution

Because keys are scoped to projects, splitting workloads across projects and keys gives you usage that maps cleanly onto teams, environments or customers.