How it Works
When you send a request to Qevron, it goes through a few stages before the response comes back. This page walks through that journey simply.
The request's journey
1. Request 2. Auth 3. Distributor 4. Provider 5. Response
───────▶ app.qevron.ai/v1 ───▶ (picks channel) ───▶ (channel) ───▶
Bearer sk-... key + group based on the OpenAI / OpenAI-format
+ quota checked model name Anthropic / response
local model- Request — Your app hits
https://app.qevron.ai/v1/...with anAuthorization: Bearer sk-...header. - Authentication — Qevron validates the key, finds its group, and checks the group's access to the model and its quota.
- Distributor — Picks a suitable channel among those serving the requested model. With multiple channels it load-balances.
- Provider — The chosen channel converts the request to the right format and forwards it to the real provider (OpenAI, Anthropic, Gemini, a local model, etc.).
- Response — The provider's response is converted back to OpenAI format and returned; usage (tokens) is recorded.
Automatic retry and failover
If a channel fails (e.g. the provider is temporarily unreachable or hits a rate limit), Qevron automatically tries to route the request to another suitable channel. This shields your app from a single provider's problems.
- Rate limit (HTTP 429) → retries after a short wait.
- Model unavailable → skips that channel, tries the next.
- All channels exhausted → returns a meaningful error (see Errors).
Key terms
| Term | Meaning |
|---|---|
| Model | The AI you request (e.g. verinova). Represents a capability. |
| Channel | The upstream source serving a model; provider + address + credential. |
| Provider | Services like OpenAI, Anthropic, Gemini. A channel's type. |
| Group | The access and quota unit for keys. |
| Token | A chunk of text the model processes; usage is measured in these. |
Next: Models · Providers · API Keys & Quota