Skip to content
ModelflareModelflareModelflare
Open CastalyConsole

Get started

Models and groups

Choose an exact model ID and a routing group that can serve it.

Two identifiers matter on every request:

  1. The model ID in the JSON body, which must match a public catalog ID exactly.
  2. The routing group bound to your API key, which decides which upstreams can serve that model.

The live catalog is Models & Pricing. This documentation site does not override prices or availability.

Exact model IDs

Section titled “Exact model IDs”

Use the ID shown on the pricing page or on the model catalog page. Do not substitute a provider marketing name, a date suffix, or a nearby variant.

Chat models that share the OpenAI-compatible Chat Completions or Responses contract are documented on Which endpoint to call and the client guides, not by duplicating one page per model. Image and video models that have their own request envelope have model pages and catalog pages.

Groups

Section titled “Groups”

Create the API key in a non-default group that lists the model. There is no single required group. If the key’s group cannot serve the model, the request fails even when the JSON is valid.

Fallback order is a property of the group, not of the request body. See Usage and cost for how charges are recorded.