Mubit
Mubit passes your app's calls on to your model provider and records them. It groups similar calls into tasks and trains adapters, small models each made for one task. Each adapter version is tested against your provider model's answers, and you can compare a passing version with your provider model in Try models.
Give your client Mubit's base URL and your Mubit key:
Your model IDs stay the same.
How it works
- Connect: give your client Mubit's base URL and your Mubit key.
- See your calls: each call shows in Requests, with its request and reply.
- Find tasks: calls with the same model, instructions, tools, tool choice and output format form a task.
- Train and test an adapter: Mubit tests each adapter version against your provider model's answers, and you can compare a passing version in Try models.
Concepts explains each term.
Start from
Your app
Send one call with the OpenAI, Anthropic or Gemini SDK, or with curl.
A coding tool
Point Claude Code, Codex, Gemini CLI or Aider at Mubit.
Past traces
Import past calls from Langfuse, Braintrust or Pydantic Logfire.
Good to know
- Calls run on your provider key, or on the starter credit where it's offered. See Provider keys.
- The examples use the host
https://api.mubit.ai. Use the base URL your console's Connect page shows.