RouteMarket Docs

How to think about lowest price, highest reliability, lowest latency, and official-only routing.

RouteMarket can accept a request-time routing preference to influence how it ranks candidate routes.

Supported first-pass values

The current design centers around these values:

Use this when your main goal is cost efficiency.

RouteMarket will prefer lower-cost eligible routes after policy and health filtering.

Good fit for:

Example:

{
  "model": "gpt-5.4",
  "routing_preference": "lowest_price"
}

Use this when success rate matters more than absolute cost.

RouteMarket will bias toward healthier and more stable routes.

Good fit for:

Example:

{
  "model": "gpt-5.4",
  "routing_preference": "highest_reliability"
}

Use this when response time matters most.

RouteMarket will bias toward lower-latency eligible routes.

Good fit for:

Example:

{
  "model": "gpt-5.4",
  "routing_preference": "lowest_latency"
}

Use this when you want RouteMarket to avoid non-official provider paths and keep routing within official-compatible sources.

Good fit for:

Example:

{
  "model": "gpt-5.4",
  "routing_preference": "official_only"
}

A routing preference is not a blind override.

RouteMarket still applies:

That means a preferred route can still be rejected if it is not allowed or not healthy.

A simple default strategy is: