Models

Use GET /v1/models to get the live catalog visible to your account. Do not infer request IDs from provider marketing names; pass the exact id returned by the API.

Endpoint

curl https://api.rout.my/v1/models \
  -H "Authorization: Bearer $ROUTMY_API_KEY"

The Authorization header is optional for public catalog browsing. With a valid key, the response can mark which models are available on your current plan.

Response

{
  "object": "list",
  "data": [
    {
      "id": "provider/model-id",
      "object": "model",
      "created": 1700000000,
      "owned_by": "provider",
      "token_multiplier": 1,
      "is_available": true
    }
  ]
}

Fields

Field	Type	Meaning
id	string	Exact model ID to send in requests.
object	string	Always model for each item.
created	number	Compatibility timestamp.
owned_by	string	Provider or model group inferred from the ID.
token_multiplier	number	Quota multiplier applied to actual token usage.
is_available	boolean	Whether your current key can use the model.

Model IDs

Model IDs are strings in a provider-scoped format:

provider/model-id

Some compatibility endpoints may accept short aliases, but the OpenAI-compatible endpoints should receive the exact id from /v1/models.

Availability

If is_available is false, the model is visible in the catalog but locked for the current account or plan. Requests to a locked model return a client error until the account has access or the request uses another available model.

Endpoint families

The model catalog is the source of truth for names and availability. Endpoint support is determined by the model type:

Model type	Primary endpoint
Chat / text / vision input	/v1/chat/completions
Embeddings	/v1/embeddings
Images	/v1/images/generations
Video	/v1/video/generations

If a model fails with model_not_found, list models again and copy the ID exactly.