Перейти к основному содержанию

Documentation Index

Fetch the complete documentation index at: https://docs.omniakey.com/llms.txt

Use this file to discover all available pages before exploring further.

StatusMeaning
400Invalid request
401Missing or invalid API key
403Account balance, API key cap, model access, or policy restriction blocks the request
404Wrong path, base URL, or model id
429OmniaKey or upstream provider throttling
500OmniaKey or upstream provider error
Correct base URLs:
ProtocolBase URL
OpenAI-compatiblehttps://api.omniakey.com/v1
Anthropic / Claude Codehttps://api.omniakey.com
Gemini-nativehttps://api.omniakey.com/v1beta

​
Quota errors

A 403 can mean the account balance is too low or the API key spending cap has been reached. Check both in the Dashboard.

​
Rate limits

OmniaKey supports route-level and model-request throttling, and upstream providers can also return 429 through the relay. Public docs do not publish fixed thresholds because limits can vary by route, account/group configuration, and provider. Treat 429 as a retryable throttling signal: retry with exponential backoff, add jitter, and avoid sending the same burst again immediately.

​
Unsupported endpoints

If an endpoint is not documented in the API Reference, treat it as unsupported for public use. This includes image generation, audio, embeddings, rerank, files, fine-tuning, and batches.