Route model calls
Mubit takes the request your app already sends to OpenAI, Anthropic, Gemini or an OpenAI-compatible service, passes it on to the provider with your provider key, and returns the provider's reply. Your app changes its base URL and sends a Mubit key. It keeps its SDK, its model IDs and its request format.
Mubit records each call by default, so the call is in Requests with its request, its reply and what served it. Recorded calls are what Mubit groups into tasks and trains adapters from.
Connect a provider
The OpenAI SDK and the Responses and chat completions APIs.
The Anthropic SDK and the Messages API.
The Google GenAI SDK and the Gemini API.
Paths, keys and headers for apps that call Mubit without an SDK.
Services that speak the OpenAI API, such as OpenRouter.
Use a Neon AI Gateway key where your workspace offers it.
To send a coding tool's calls through Mubit, see Coding tools. For a framework, see Frameworks.
What else is in this section
- Keep your model IDs: your app keeps the model IDs it sends today.
- Find calls in Requests: filter the list, read a call and its session, and see why a call isn't listed.
- Troubleshooting: an error's code and the fix.
- API reference: paths, headers, limits and errors for every provider prefix.
New here? Start with the Quickstart.