oorr / api platform
.open {API}

DEVELOPER PLATFORM09 — Usage

Usage UI only

OORR API Platform Sargon 1.5

No usage API exists — these tiles cannot be populated

Usage is recorded server-side, but the deployed API exposes no endpoint that reads it back: there is no per-caller totals endpoint, no usage-history endpoint and no cost aggregation. The panel below is the interface shell only. It shows no numbers because there are no real numbers to show, and it will not invent any.

Usage summary

Awaiting backend

Current Asia/Baghdad day. Requires GET /api/usage/summary.

API requests
—Count of API requests.
Input tokens
—Sum of inputTokens.
Output tokens
—Sum of outputTokens.
Total tokens
—The allowance-accounted figure.
Current cost
—Not computed anywhere in the service.

Usage history

DateRequestsInputOutputTotalCost
No data source. A history endpoint is not implemented.

What already exists server-side

Every request is metered with the fields below. Building the panel above is a matter of exposing a read endpoint over this table — the measurement layer is already in place and is billing-ready in the sense that input and output tokens are stored separately per call.

Metered per request
{
  "id":           "uuid",
  "userId":       "student_4821",
  "model":        "sargon-1.5",
  "inputTokens":  412,
  "outputTokens": 735,
  "totalTokens":  1147,
  "latencyMs":    4210,
  "success":      true,
  "createdAt":    "2026-09-23T09:14:02.441Z",
  "requestType":  "text"
}

Only same-day totals per caller are aggregated today, and only for the allowance check. Per-key attribution, multi-day history and cost rollups all require the API-key work described next.