Overview
The models endpoint returns a list of all available models that can be used with the Helicone AI Gateway. This endpoint is OpenAI-compatible and returns models in the same format as OpenAI’s/v1/models endpoint.
Authentication
This endpoint does not require authentication and can be called without an API key.Endpoint
Request
This endpoint accepts no query parameters and returns all available models.Response Format
Always returns
list to indicate this is a list response.Array of model objects available through the gateway.
Example Response
Model Filtering
The endpoint automatically filters out models that:- Require explicit routing configuration
- Are not available through the standard gateway endpoints
- Have no registered endpoints in the cost registry
Using Model IDs
Theid field from each model object can be used directly in your chat completion requests:
Model Support
The Helicone AI Gateway supports models from multiple providers:- OpenAI: GPT-4, GPT-3.5, and variants
- Anthropic: Claude 3 family (Opus, Sonnet, Haiku)
- Google: Gemini models
- Meta: Llama models
- Mistral: Mistral and Mixtral models
- And many more: The registry is continuously updated with new models
Error Handling
Error information if the request fails.
Example Error Response
Implementation Details
The models list is generated from Helicone’s internal cost registry (@helicone-package/cost/models/registry), which:
- Tracks pricing and capabilities for each model
- Is automatically synced with provider model releases
- Includes metadata like creation dates and ownership
- Powers cost calculation and analytics in Helicone
Rate Limits
This endpoint has generous rate limits as it’s a read-only operation that doesn’t consume compute resources. It can be called frequently for model discovery without concerns about rate limiting.Best Practices
- Cache the response: The model list doesn’t change frequently, so cache it client-side to reduce API calls
- Filter by provider: If you only use specific providers, filter the response by the
owned_byfield - Dynamic model selection: Use this endpoint to build dynamic model selection UIs
- Validation: Validate user-provided model IDs against this list before making completion requests
Client-Side Filtering Example
Related Endpoints
- Chat Completions - Use models from this list to create completions