Skip to main content
The AI Gateway speaks the APIs your code already uses. Point your client at Altrum, send a virtual key instead of a provider key, and keep the rest of your code. Requests and replies keep the shape of the API you called.

​
Base URLs

The OpenAI endpoints also answer under https://api.altrum.ai/openai/v1, for clients that expect that prefix. Cursor has its own base URL: see Coding agents. Any format can reach any provider your organization has a credential for. A request in the OpenAI format can be answered by an Anthropic model: Altrum converts it, and the reply comes back in the OpenAI format.

​
Name a model

Name the provider, a slash, and the model: If you leave the provider out, Altrum picks one your organization can reach for that model. When none can, the request is refused with status 400 and the message could not auto resolve a provider for the request, please specify a provider explicitly. Add the provider to the model name. Your organization may serve only the models it approved: see Model catalog. List models returns the models your key may use.

​
Fallbacks

Add fallbacks to any request body to name models to try, in order, if the first one fails:
The response header x-alt-fallback-index tells you which one answered. See Models and routing.

​
Not served

The AI Gateway does not serve embeddings, images, audio, video, batches, files or realtime sessions, and it does not store responses for you to fetch later. A request to any of those paths gets a 404.