SimpleLLMDocs
HTTP API
Markdown ↗

Read account usage and balance

GET /v1/usage

Daily usage for the last 30 days, current balance and lifetime total_spent in SC. This route has no date or granularity query filters.

Base URL: https://api.simplellm.eu. Authenticate using Authorization: Bearer $SIMPLELLM_API_KEY.

Example request

bash
curl --fail-with-body https://api.simplellm.eu/v1/usage \
  -H "Authorization: Bearer $SIMPLELLM_API_KEY"

Responses

HTTP 200

Successful response

Content-Type: application/json

FieldTypeRequiredMeaning
usagearray<AccountDailyUsage>No
usage[].user_idstringNo
usage[].datestringNo
usage[].modelstringNo
usage[].requestsintegerNo
usage[].tokens_inintegerNo
usage[].tokens_outintegerNo
usage[].tokens_cachedintegerNo
usage[].cost_scnumberNo
balancenumberNo
total_spentnumberNo

Illustrative response shape only; IDs, timestamps and counters below are synthetic, not live limits or customer data.

json
{
  "usage": [
    {
      "user_id": "00000000-0000-4000-8000-000000000000",
      "date": "2026-09-14T00:00:00Z",
      "model": "qwen3.8-flash-next",
      "requests": 0,
      "tokens_in": 0,
      "tokens_out": 0,
      "tokens_cached": 0,
      "cost_sc": 0
    }
  ],
  "balance": 0,
  "total_spent": 0
}

Error handling

Errors can occur in authentication, billing, routing or the upstream service; not every status applies to every route.

StatusMeaning
400Invalid request
401Invalid credentials
402Insufficient credits
403Access denied
404Model or resource not found
429Rate or capacity limit
500Internal error
502Routing or upstream error
503Temporarily unavailable
504Deployment timeout

See Troubleshooting for response examples and Rate limits & retries for retry rules.

Machine-readable schema

Download OpenAPI JSON. Operation ID: getUsage.

Search the complete documentation.