Skip to content

Add Tium's five models to model-metadata.json - #5697

Open
curiousbox wants to merge 1 commit into
Aider-AI:mainfrom
curiousbox:feat/add-tium-models
Open

Add Tium's five models to model-metadata.json#5697
curiousbox wants to merge 1 commit into
Aider-AI:mainfrom
curiousbox:feat/add-tium-models

Conversation

@curiousbox

@curiousbox curiousbox commented Sep 9, 2026

Copy link
Copy Markdown

Adds five Tium models to model-metadata.json.

Tium is an OpenAI-compatible gateway for open-weight models. Reached through OPENAI_API_BASE, its models are named without a provider prefix, for example glm-5.3-flash. That matches no entry in litellm's cost map, so aider reports "Unknown context window size and costs" and a session cost of $0.00.

The openai/ keys are what that path looks up, which is why a cost-map entry under a vendor prefix does not cover it. litellm already catalogues some of these models under zai/ and openrouter/z-ai/; those resolve for users of those providers, not this one.

Every figure is derived from the gateway's GET /v1/models rather than typed in: input is the published rate times the model multiplier, output is input times the published output weight. Context and max output are the served ceilings, not the models' upstream maximums, which are higher.

The two DeepSeek entries are marked supports_tool_choice: false because DeepSeek refuses tool_choice="required" while reasoning is enabled. Function calling and prompt caching work on all five.

Verified by running aider against the modified file with no local .aider.model.metadata.json present: the warning is replaced by a resolved model.

Tium is an OpenAI-compatible gateway for open-weight models. Reached through
OPENAI_API_BASE, its models are named without a provider prefix, for example
`glm-5.3-flash`. That matches no entry in litellm's cost map, so aider reports
"Unknown context window size and costs" and a session cost of $0.00.

The `openai/` keys are what that path looks up, which is why a cost-map entry
under a vendor prefix does not cover it. litellm already catalogues some of
these models under `zai/` and `openrouter/z-ai/`; those resolve for users of
those providers, not this one.

Every figure is derived from the gateway's GET /v1/models rather than typed in:
input is the published rate times the model multiplier, output is input times
the published output weight. Context and max output are the served ceilings,
not the models' upstream maximums, which are higher.

The two DeepSeek entries are marked supports_tool_choice: false because DeepSeek
refuses tool_choice="required" while reasoning is enabled. Function calling and
prompt caching work on all five.

Verified by running aider against the modified file with no local
.aider.model.metadata.json present: the warning is replaced by a resolved model.
@CLAassistant

CLAassistant commented Sep 9, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants