Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content
Guides

Keep your model IDs

You don't change the model IDs in your code. Send the IDs you send today, such as gpt-6-luna, claude-haiku-4-5 or gemini-3.8-flash.

What Mubit does with a model ID

  • It passes the ID on. When Mubit sends a call to your provider, it sends your model ID as your app wrote it.
  • It records the ID. In Requests, Model asked shows the model ID of each call.
  • It counts the model in the task. Calls form one task when they share their instructions, tools, tool choice, output format and model. So the same instructions sent to two different models make two tasks.

Mubit reads the model without its date or snapshot suffix, and without -latest. For example, claude-haiku-4-5-20251001 and claude-haiku-4-5 count as one model, and so do gpt-5.5-2026-04-23 and gpt-5.5.

On Gemini, the model ID is in the path, as in /v1beta/models/gemini-3.8-flash:generateContent. Mubit reads it from there.

On the starter credit

The starter credit serves a set list of models for each provider it covers. A call that names another model gets 400 starter_credit_model, and the message lists the models it serves. A dated ID works only when that list names it.

With your own provider key, you can use any model your provider account can use. See Provider keys.

What you can't do with a model ID

There is no Mubit model ID: you can't send a call to an adapter by naming it as the model. To try an adapter, compare it in Try models: see Compare with your provider.