Overview
The Models API exposes the models that the connected Allternit runtime can serve, along with routing policy aliases and a cross-provider pricing snapshot. Model listings are filtered by the virtual key’s allowlist, so callers only see models they are permitted to use.Base URL
Endpoints
List models
Example response
Model object fields
Policy aliases
Policy aliases are synthetic models that trigger the gateway’s benchmark-weighted router. The router picks a concrete provider/model pair and derives a cross-provider fallback chain.Retrieve a model
404 with code allternit.model_not_found.
Pricing
GET /v1/pricing returns the current per-model rates in dollars per 1 million tokens.
Pricing fields
Error codes
Related pages
- Chat Completions — use models and aliases in completions
- Proxy — how the gateway routes model requests
- Translate — wire-format translation details