Your privacy choices

We use essential storage to operate Lexel Translate. With your permission, we also use analytics, advertising, and marketing technologies. Read our Cookie Policy.

Usage

Inspect quota consumption over time for a personal account, organization, or API key. Session auth only.

Endpoint

GET/api/v1/usage/summary

Return usage summaries and recent raw usage events.

Request example

curl -X GET "https://translate.lexel.ai/api/v1/usage/summary?scope=user&window=daily&limit=30" \
  -H "Cookie: better-auth.session_token=your_session_cookie"

Query fields

Field	Type	Required	Description
scope	user \| organization \| api_key	No	Scope to summarize. Defaults to the current actor scope.
scope_id	string	No	Explicit organization or API key ID when summarizing a child scope.
window	daily \| monthly	No	Aggregation window. Defaults to daily.
limit	integer <= 180	No	How many summary rows to return.
service	string	No	Optional service filter such as translation.
operation	string	No	Optional operation filter such as translate or detect.

Response fields

Field	Type	Required	Description
ok	boolean	Yes	True when the summary is returned.
scope	user \| organization \| api_key	Yes	Resolved scope kind.
ownerType	user \| organization \| api_key	Yes	Underlying owner bucket used for usage aggregation.
ownerId	string	Yes	Resolved owner identifier.
currentPeriodKey	string	Yes	Current daily or monthly key.
currentSummary	array	Yes	Rows for the current daily or monthly period.
rows	array	Yes	Requested historical summary rows.
recentEvents	array	Yes	Recent usage-event records for the same resolved scope.

Response example

json

{
  "ok": true,
  "scope": "user",
  "ownerType": "user",
  "ownerId": "usr_123",
  "currentPeriodKey": "2026-07-09",
  "currentSummary": [
    {
      "dayKey": "2026-07-09",
      "service": "translation",
      "operation": "translate",
      "inputCharacters": 3200,
      "outputCharacters": 3814,
      "requestCount": 14
    }
  ],
  "rows": [],
  "recentEvents": []
}

Next steps

Programmatic translation clients normally rely on translate-route usage fields for per-request accounting. Document translation consumes Premium characters, whether submitted through the API or the signed-in browser interface.