Skip to main content

Automatic routing

With automatic routing, your app sends model: "auto", or sends no model, and Proxium chooses the tier for each call. A short greeting can go to a cheap tier, and a long coding task to a strong tier. Your app does not decide.

auto has no models of its own. Proxium classifies the call, or it uses the tier standard.

When Proxium classifies​

Proxium classifies a call for auto when the project can reach a classifier. A project has a classifier in one of these cases:

The project hasThe classifier is
A preset (see Ready-made routing)Your own Jev if you added a TypeSafe vendor, then a small model of your vendor
Its own vendor in the classifier tier, set on RoutingThat vendor
The grant of the classifier of Proxium, from the adminThe Jev of Proxium, then a small model of Proxium

A project with none of these does not classify. Each call for auto uses the tier standard, and Proxium makes no classifier call.

A project with the grant: every text tier​

A project can have the grant of the classifier of Proxium. In that project, the classifier also chooses the tier of a call that names a text tier, such as standard or heavy. So the classifier routes every text call of the project, whatever tier the app sends. If the classifier gives no answer, the call keeps the tier that it named.

The classifier does not change these calls:

  • A call that names a model, such as ollama/glm-5.3-flash. The call gets that model.
  • A call for vision, and a call that sends an image, audio or video. The classifier chooses from text tiers only.
  • Embeddings, and the calls of image, speech and video.

:::info State on proxium.tech The classifier of Proxium is not free for customers. The admin grants it to one project, or to every project of a plan. Without the grant, a project classifies only with its own vendor. :::

How it works​

Fig. 1 · how model auto chooses a tier

For a project with a classifier:

  1. Your app sends model: "auto", or no model.
  2. Proxium sends the last user message to the classifier. For a long message, it sends the start and the end.
  3. The classifier names one tier of the preset: trivial, standard, high, heavy or code. Example: a long coding task gets heavy.
  4. Proxium calls the models of that tier, with the normal rules: app, key, project, default.

If the classifier fails, or the call has no user message, Proxium uses the tier standard.

The classifier never makes a call fail. Proxium uses the tier standard in each of these cases:

  • The project has no classifier.
  • The classifier fails, or it is less sure than the minimum confidence and no other step decides.
  • The call has no user message.
  • The key or the project is at one of its limits.
  • The operator turned the classifier off.

Ready-made routing​

On Routing, the Ready-made routing section lists a preset for each vendor of the project. Proxium writes nothing until you select Use this preset. A preset holds:

  • the tiers trivial, standard, high, heavy, code, with a description of each that the classifier reads
  • the models of each tier, from that vendor, best first
  • the classifier tier: your own Jev if you added a TypeSafe vendor, then a small model of your vendor

A preset exists for these vendors: OpenAI, Anthropic, Google Gemini, Mistral, DeepSeek, Groq, Together AI and OpenRouter. Each provider page under Providers shows the models of its preset.

You doProxium does
Select Use this presetWrites the preset of that vendor
Use the mixed preset, with vendors at several providersWrites, for each tier, the first choice of each vendor, cheapest first, then their other models, cheapest first
Use a preset with a TypeSafe vendor in the projectPuts your own Jev first in the classifier tier
Set the models of a tier yourselfKeeps your models. A preset never writes a tier that you set
Select Copy and editMakes the models of the preset your own. A new version of the preset no longer changes them
Select Reset to the presetWrites every tier of the preset, the tiers that you set included

When Proxium releases a new version of a preset, each project on that preset gets it at the next start of the gateway. A project that selected Copy and edit keeps its models.

A project that uses no preset keeps its own routing. It classifies auto only with its own vendor in the classifier tier, or with the grant. Otherwise auto uses the tier standard.

The classifier of a preset​

You bring the classifier. Proxium suggests one of two kinds:

StepModelKey
1Jev, from TypeSafe, a model made to classify. Add it under Providers as the vendor TypeSafe (Jev classifier)Your TypeSafe key
2A small model of your vendorYour vendor key

Jev decides when it is sure enough. Otherwise step 2 decides. If both fail, Proxium uses the tier standard. The classifier never tries a large model of your vendor.

proxium.tech does not offer its own Jev to customers by default. The admin can grant it to one project, or to every project of a plan.

Two kinds of classifier​

KindWhat it getsWhat it answers
A chat modelA prompt that asks for one word, a tier nameThe tier name
Jev, from TypeSafeThe user text, and the tiers with a description of eachA tier and a confidence

The classifier tier can hold both kinds. The kind that comes first in the tier runs first. If it fails, or Jev is less sure than the minimum confidence, the other kind decides. Each preset sets its own minimum confidence. A project with no preset uses the minimum confidence of the gateway.

See why a model answered​

On Requests, the Asked for column of an auto call shows the tier that the classifier chose, for example auto → code. When Jev chose the tier, the column also shows the confidence of Jev: auto → heavy (90%).

What it costs​

The classifier call is a real model call. Proxium records its cost against your project, like any call. A key that reached one of its limits skips the classifier, because Proxium refuses that call anyway.