Calls an adapter answers
Once a task has a version in its rollout, Mubit can answer some of the task's calls with the adapter instead of your provider. Your app changes nothing: it sends the same request with the same model ID. This page links the rollout to the calls a version answers, and shows how to read in the console who answered each call. It is for developers who need to know which model answered.
Which versions answer calls
| Step | What the version answers |
|---|---|
| Silent test | Copies of the task's calls, after your provider has answered. Your app never sees these replies. |
| Partial rollout | Its share of the task's conversations. A conversation stays with one version. |
| Live | Every call of the task it can take that the partial rollout doesn't. |
The rollout explains each step.
Which calls, and how a call reaches an adapter
Calls answered by an adapter is the one place for the routing rules. It lists the calls an adapter can answer today, the checks Mubit makes before an adapter answers a call, the x-middleware-served-by header on an answer an adapter gave, and the copies Mubit sends to your provider to compare the replies.
In short: today only Chat Completions calls on /openai/v1, with an OpenAI key or a Neon AI Gateway key, recorded in full, can go to an adapter. An answer an adapter gave carries x-middleware-served-by, whose value names the version that answered (version=<n>). An answer from your provider doesn't carry it.
Read who answered in Requests
Requests shows who answered each call under Served by:
| Served by | Who answered |
|---|---|
Your provider | The model your app named. |
Your adapter (v{n}) | Version n of the task's adapter. |
Prompt only | The base model with the task's instructions, for a version whose result is Prompt only. |
· below its test after the name means that version didn't pass its exam: see How the exam acts today. The Served by filter lists the calls one of them answered.
Turn on Include copies to list the calls your app didn't see as well:
| Row | What it is |
|---|---|
Silent-test copy | A version's reply to a copy of a call, in a silent test. |
Spot-check copy | Your provider model's reply to a copy of a call an adapter answered, made to compare the two. Your provider bills it. |
Set-aside reply | An adapter's reply that failed Mubit's checks. The call it belongs to says Your adapter's reply was set aside., and your provider answered it. |
Keep calls on your provider
| To keep | How | What else changes |
|---|---|---|
| One call | Send x-middleware-record: metadata or off, or x-middleware-store: false. | Mubit doesn't record the call's content, so the call is not rated and trains nothing. |
| A task's calls | An admin selects Switch off… on the adapter's page. | Every version is kept. Switch on… brings them back. |
| A task's calls, from one version | Take the version offline, or roll back. See The rollout. | The version stays listed. |
Nothing turns adapters off for a whole project at once.
Calls an adapter answers are recorded like any other call, and can be rated. Rate the replies you know are wrong: see Rate a call yourself.
Next
- Costs and data: what runs on your provider key, and where call content goes.
- What to expect: the limits you can meet.