Prisijungti Registruotis
Arbebus API

Usage

Real sandbox metering in the Developer Platform database. Token fields are reserved until real AI API integration.

Request units

Accepted sandbox ping executions consume 1 request unit. Quota rejections, auth failures, and successful idempotency replays record 0 consumed units.

Latency

Server-side monotonic timing from request boundary to response construction, stored as integer milliseconds. Clients cannot supply latency values.

Tokens

input_tokens, output_tokens, and total_tokens are nullable and unused until real AI product APIs are connected. The dashboard shows “Not available yet” when no token data exists. Values are never fabricated.

Dashboard

/dashboard/usage.html shows real authenticated sandbox usage for the selected organization, project, and environment. Empty states are shown when no events exist. No fake statistics.

Portal APIs

  • GET /api/developer/v1/usage/summary
  • GET /api/developer/v1/usage/timeseries
  • GET /api/developer/v1/usage/events

These require a Supabase user session and organization membership. They never return API key secrets, hashes, Authorization headers, or request bodies.