Skip to main content
Use the /v3/models endpoint to retrieve all LLM models available through Eden AI, along with their capabilities: input modalities, reasoning, web search, and function calling.

Endpoint

The endpoint is public: no API key is required.

Example

Response

Each entry includes the model’s identity, context window, capabilities, pricing, available regions, and whether the provider retains your data (list truncated for readability):
Each model id is used directly as the model parameter in your requests. pricing holds the rates a call bills at, after any discount, and list_pricing the provider’s list rates before it, most of them in US dollars per token. OpenAI models that can run as a batch also carry input_cost_per_token_batches, output_cost_per_token_batches and cache_read_input_token_cost_batches, the rates a batch bills at when the model has them.

Grouped view: one entry per routable name

Many models are sold by more than one provider. Pass view=models to get one entry per routable model name, with the provider endpoints nested underneath. This is how you discover the names that Provider Routing accepts.
cURL
The key is optional here: without one, the listing holds the catalog only.
What to expect from the shape:
  • id is the routable name. Send it as model and Eden AI picks which provider serves it.
  • Top-level fields summarise the model across its endpoints. context_length is the largest window among the endpoints. capabilities is the union across endpoints, so a flag is true and a modality listed when any endpoint supports it. pricing carries the full price list of the cheapest endpoint for a typical call (untagged endpoints only, since an @region variant prices a tagged call), identified by pricing_endpoint; both are null when no endpoint has a price. A routed call is billed at the prices of the provider that served it. regions lists every region where at least one endpoint runs, sorted by code.
  • Each entry in endpoints is the same object the default view returns, with that provider’s own pricing, capabilities, context length, and regions. To compare providers or see per-provider values, read endpoints.
  • owned_by changes meaning between the views. On a grouped entry it is who authored the model (openai); on an endpoint entry it is the provider selling it (azure).
  • created is the newest endpoint’s timestamp, and endpoint_count equals endpoints.length.
  • The default (view=endpoints, or no parameter) is unchanged, and both entry shapes stay compatible with the OpenAI SDK’s client.models.list().
  • Your routing policies are listed here too. Send your API key and the grouped view adds one entry per routing policy you can call, under its policy/{name} id, with owned_by set to edenai, an empty endpoints list and endpoint_count at 0: which target serves a call is decided per request, so pricing, context_length and regions are null or empty. Policies never appear in the default view or under a zero_data_retention filter.
Every model listing takes the same parameter: /v3/models, /v3/embeddings/models, /v3/moderations/models, /v3/audio/transcriptions/models, /v3/audio/speech/models, /v3/images/models, /v3/videos/models and /v3/rerank/models.

Zero Data Retention

Every endpoint entry (each entry of the default view, and each item of endpoints with view=models) carries zero_data_retention, which says whether that provider keeps your prompts and outputs after the response, for the calls Eden AI sends it: The value is set per provider, and per model when one model’s terms differ from its provider’s. Models served from your own private deployment are always true. See Provider Data Policies for how each provider handles your data. To list only Zero Data Retention endpoints, pass zero_data_retention=true:
cURL
zero_data_retention=false lists only the endpoints known to keep data, and entries still at null match neither. With view=models, each model keeps only its matching endpoints and recomputes its model-level fields from them, and is left out when none match. Every model listing above takes the parameter.

Model aliases

Some models are available under a stable alias, a version-agnostic name that always points to the current release, alongside versioned or dated snapshot IDs:
  • Stable alias: google/gemini-flash-latest, anthropic/claude-sonnet-latest, deepseek/deepseek-chat
  • Versioned snapshot: anthropic/claude-opus-4-5-20251101
Use the stable alias when you want your integration to keep working as providers ship new versions. Pin a versioned snapshot when you need a fixed, reproducible model. Either form works as the model parameter. Alias entries report the concrete model they currently resolve to in the alias_of field, as in the response example above. The catalog lists both forms when a provider exposes them, so you may see a stable alias (e.g. anthropic/claude-opus-4-5) and one or more dated snapshots (e.g. anthropic/claude-opus-4-5-20251101) side by side. Use the stable alias to always get the latest version, or a dated snapshot to pin to a specific release.

Capabilities

The capabilities object describes what each model supports: Some models expose extra provider-specific keys (e.g. supports_pdf_input, supports_audio_input), and a few return "capabilities": null. Treat a missing key or a null object as “not supported”.
You can also browse all features and providers visually in the Eden AI model catalog.
Need EU data residency? Hit https://api.eu.edenai.run/v3/models instead and the list is automatically filtered to EU-eligible models. See EU Endpoint.
Looking for OCR, image, or audio models? See List Expert Models for the full catalog of expert model features.