Orux AI ·
A multi-model API can let one account call several supported models. The key simplifies access, but you must still select a valid model and follow its input, capability and billing rules.
Can one API key access text, image, video and audio models?
On Orux AI, one eligible API key can call supported models permitted by that key, subject to account balance and usage limits. This simplifies account access; it does not mean every model uses the same input or returns the same response format.
Use the model catalog to identify a currently available model and its supported operation. Text requests commonly use chat completions, while generation jobs may use asynchronous tasks. Follow the model's API example instead of changing only the model name in an unrelated request.
How do I switch between models without rebuilding my application?
Separate your application prompt and business logic from the API client configuration. Store the base URL, API key and selected model alias in server-side configuration. For models using the same supported endpoint, a model change can then be small.
Before switching, test tool definitions, response parsing, context limits, image inputs and generation parameters. Keep a per-model capability check where features differ. OpenAI-compatible access reduces some integration work, but does not remove the need for model-specific testing. See OpenAI-compatible APIs explained.
Does one API key mean one price for every model?
No. A shared key identifies your account; it does not make different models cost the same. Orux uses Credits for billing, with the model page showing the relevant unit and specification. Text, image and video workloads can have different billing units.
Keep the model alias, request settings and final usage record together when comparing costs. Changing video duration, resolution or output length may change the charge even if the API key stays the same. View current pricing.
How should I protect a key used by several AI features?
Keep the key on your server and use an environment variable or a secret manager. Do not put it in a public repository, browser bundle, screenshot or shared prompt. Apply the key permissions and limits needed for your application, and revoke a key if it is exposed.
For larger projects, separate production and development credentials so test traffic is easier to identify and limit. One-key access is a convenience, not a requirement to share one credential across every team or environment. Orux keys are shown in full when created; store that value safely rather than assuming it can be recovered later.