OpenRouter’s Jev Router chooses a model and reasoning effort for each request. Jev assesses the task; a routing policy combines that assessment with estimated cost, model capabilities and caller restrictions. The chosen generative model writes the response.

Its primary documentation makes a consequential distinction between model preferences and enforced boundaries.

An include list can be relaxed

According to OpenRouter, models and its alias allowed_models are include preferences with fallback:

  • If they match catalog models but leave no eligible route, the router retries without the includes.
  • If none of the entries matches a public text model in the catalog, the request fails with 404.
  • excluded_models remains enforced through fallback. Excluding every available model produces an error.

A list such as models: ["anthropic/*"] can therefore fall back to another author. Applications with a strict author restriction need an actual enforced boundary.

OpenRouter separately documents author-router aliases such as anthropic/auto, when available in the catalog. Their author scope remains enforced when includes are relaxed. Author scope concerns the model maker; a separate provider can still serve that model.

Cost and effort settings leave room for policy

The documented low, medium and high cost tiers express routing priorities. They provide neither a per-request price cap nor a guaranteed model or quality score.

Likewise, reasoning.effort supplies a hint. OpenRouter says the router may choose another effort or adapt it across turns. Supported agent workflows may retain a model, switch models or add an expert advisor.

These are documented behaviors, without a reproduced API trial or a measured savings claim here.

Inspect the route that actually served the request

The response’s model field identifies the serving model. OpenRouter documents more detail when callers send X-OpenRouter-Metadata: enabled:

  • resolved_models records selected models in fallback order.
  • candidates includes effort, capability tier and estimated cost; estimates differ from the final bill.
  • list_fallback: "models_ignored" signals relaxed includes.
  • list_tier_cap signals a lowered capability requirement after list restrictions.

Treat those traces as part of evaluating the complete routing policy. A typed Jev decision still needs evidence that the selected model handles the task correctly.

Caveat: this is a review of the complete vendor documentation, without live requests, source-code inspection or independent validation of routing quality.