Usage Administration

Usage Administration is the cross-tenant fleet view — where Platform Operations answer questions like "which tenants ran the most policy evaluations in the last hour" or "which clusters emitted no telemetry today". The /usage route on the control plane serves this view. It reads the tenant roster (GET /tenants, GET /tenants/stats) live from the tenants module for the tenant count, active-tenant count, and subscription-tier distribution across the fleet.

For per-tenant consumption the control plane pulls rated usage from the billing module's rating engine and joins it to the tenant list. That path is now real end to end: data planes emit per-event rows into gcdm_usage_events via the Local Usage Journal (see the Billing and Credits capability), the hourly Usage Aggregator rolls them into gcdm_usage_rollups, and heartbeats to the control plane populate control_plane_usage_events with the rated credits under the launch price book (launch-2026-08). The /usage page groups those into total credits, per-meter breakdown, and per-tier distribution.

The per-tenant self-service view at /t/:slug/usage is the tenant-facing counterpart. It surfaces the same figures scoped to one tenant, with a link into the AI Cockpit Metering & Billing tab for the drill-down view.

Billing mode — PAYGO, Credits, or ULA — is now a real field on the tenant record (billing_mode on gcdm_tenants), populated at tenant creation and readable by the /usage page. Earlier builds always fell back to a hardcoded "PAYGO" default because the field didn't exist; that gap is closed as of the 2026-08 pricing rollout.

Staff have full visibility here; tenant-side users only see their own row. Nothing on this page ever shows another tenant's numbers to a tenant user — the API layer scopes every query by tenant ID, not by the frontend's rendering choices.