API Keys & Quota

This page explains how keys are organized and how quotas and rate limits work.

Keys and groups

Every API key belongs to a group. The group defines the key's permissions:

• Accessible models — The group can only access certain model sets.
• Quota — Total spendable balance/usage.
• Rate limits — Requests per minute (RPM) and tokens per minute (TPM).
• IP restrictions (optional) — The key can only be used from certain IP ranges.

This structure lets a team hand out separate, quota-limited keys to different users/apps.

Rate limits

Every response returns headers showing your rate-limit status:

X-RateLimit-Limit-Requests: 1000
X-RateLimit-Remaining-Requests: 987
X-RateLimit-Reset-Requests: 1716200600
X-RateLimit-Limit-Tokens: 200000
X-RateLimit-Remaining-Tokens: 194300
X-RateLimit-Reset-Tokens: 1716200600

Header	Meaning
*-Limit-Requests	Allowed requests per period
*-Remaining-Requests	Remaining requests
*-Reset-Requests	When counters reset (Unix seconds)
*-Limit-Tokens / *-Remaining-Tokens / *-Reset-Tokens	Token-based equivalents

If you exceed a limit you get 429 Too Many Requests. Wait a short while and retry (e.g. until the Reset time).

Querying usage

You can view your current quota and spend programmatically:

# Remaining quota / subscription
curl https://app.qevron.ai/v1/dashboard/billing/subscription \
  -H "Authorization: Bearer $QEVRON_API_KEY"

# Total usage
curl https://app.qevron.ai/v1/dashboard/billing/usage \
  -H "Authorization: Bearer $QEVRON_API_KEY"

Details: Billing / Usage API.

How is usage measured?

Usage is token-based. The usage field in every response shows your spend:

"usage": {
  "prompt_tokens": 18,
  "completion_tokens": 16,
  "total_tokens": 34
}

• prompt_tokens — Token count of the input you sent.
• completion_tokens — Token count of the response the model produced.
• total_tokens — The sum.

When streaming, add stream_options: { "include_usage": true } to get usage info (see Streaming).