SMART ROUTING
Choose the lowest-cost available route within the correct model boundary
A smart group is not another model. It selects among token groups that support the requested model and are available to the current user.
Last updated:
How smart routing works
Select a smart group when creating the key, but continue sending a real model ID. 懂api filters compatible token groups, ranks them by the user's effective multiplier, and tries them in order.
- Validate the model against the smart group's capability boundary.
- Read enabled channels and token groups for that model.
- Remove unavailable groups, invalid multipliers, and incompatible image groups.
- Rank the remaining groups by effective user price.
Two smart text groups
| Token group | Allowed | Excluded |
|---|---|---|
smart:gpt | GPT, Codex, Cursor, and OpenAI text/reasoning models | Image, video, Claude, GPT作图 |
smart:claude | Claude text models | Image and video models |
Images and videos use regular groups
Smart GPT Image and Smart Seedance have been retired. Edit any old key in API Keys and select a regular image or video group supported by the live catalog, such as a supported GPT作图 or Seedance group. 懂api never silently switches to a differently priced group, and historical tasks and results are preserved.
Select a regular group to fix the route. Smart GPT and Claude follow their published failover rules across candidate groups. See Group selection and questions for the group guide.
Selection uses the user's effective multiplier
The same model may be available in several token groups. 懂api ranks the current user's effective route-to-group multiplier, not a single marketing number.
A cheaper group that does not support the model never becomes a candidate. The public catalog follows the same rule.
Which failures trigger failover
Rate limits, transient upstream errors, overloads, selected 5xx responses, and equivalent transient errors wrapped in HTTP 200 can move to the next candidate. Invalid parameters, policy refusals, and context-length errors do not trigger blind retries.
Failover is bounded to prevent request loops. A client disconnect is not treated as an upstream failure.
Verify the selected route
- The visible group remains the smart group selected by the user.
-
selected_grouprecords the concrete token group that completed billing. - Recovered intermediate attempts are hidden from the default log list.
- An administrator can inspect the full attempt chain by exact request ID.