Skip to main content

Models

RouterLink exposes the current model catalog from its live registry. The catalog size changes as models and provider channels are added, updated, or deprecated, so use the total field from GET /api/v1/models as the source of truth instead of hardcoding a model count. Browse the full catalog at https://routerlink.ai/models.

API Reference

List Models

Retrieves a paginated list of logical models with metadata, capability tags, provider-channel aliases, and context/output limits.

Parameters

For array parameters, pass repeated query keys, for example vendors=OpenAI&vendors=Google.

Example

Response

The values above are an example response shape. The live catalog can change.

Model Group

Returns the provider-channel implementations for a given logical model, grouped by RouterLink format standard and provider-channel alias. This powers model detail pages where users can see which channels can serve a model.

Response Shape

Currently, the public GET /api/v1/{model_standard}/models route accepts RouterLink format standards such as OpenAI and Anthropic. Use /api/v1/models/group when you need the grouped view for a logical model.

Providers List

Returns all available provider-channel aliases, sorted alphabetically. Provider-channel aliases are routing channels, not necessarily model vendors.
Example values include OpenAI Channel, Anthropic Channel, GCP Vertex, WORLD3 Router North America, and WORLD3 Router Asia Pacific.

Vendors List

Returns all unique vendor names, sorted alphabetically. Vendors are the model owners or model families, such as OpenAI, Anthropic, Google, DeepSeek, Qwen, and others.

Model Labels

Models on routerlink.ai/models are tagged with labels to help you choose the right one:

Pricing

RouterLink stores pricing as per-model, per-provider-channel, per-token-type tiers in the model_pricing table. Pricing is returned by endpoints that expose model implementations, such as GET /api/v1/models/group and GET /api/v1/{model_standard}/models?with_price=true. Each pricing entry contains: Supported token types are defined by the registry and currently include: A price of 0 means the tier is free.

Chat Completion Request Parameters

When calling POST /api/v1/chat/completions, supported parameters depend on the target model and provider channel. Common OpenAI-compatible parameters include: Provider-specific extra fields may be accepted by some channels, but portable behavior should be based on the parameters above and the target model’s capabilities.

Data Model

RouterLink maintains a unified MySQL registry across three core tables: A fourth table, model_fallback_chains, defines provider failover behavior. When a primary provider is exhausted, the gateway can try the next enabled fallback entry ordered by priority.

Providers and Vendors

RouterLink separates provider channels from vendors: Use GET /api/v1/models/providers and GET /api/v1/models/vendors to retrieve the current live lists.