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

Costs and data

Training and testing adapters makes some calls of its own. This page says which of them your provider bills you for, and where the content of your calls goes. It is for whoever owns your provider bill, and for anyone who answers questions about your data.

What runs on your provider key

Your provider bills you for these calls, on the provider key your project uses:

  • Calls your provider answers. Every call an adapter doesn't answer goes to your provider as usual, including a call whose adapter reply Mubit set aside.
  • Spot-check copies. While a version answers calls in a partial rollout or live, Mubit asks your provider model a sample of the same calls again, to compare the replies. By default that is about 2% of the calls each version answers, at least 10 and at most 500 a day.
  • Silent-test references. A silent test compares the new version's reply with your provider model's. When the live version, and not your provider, answered the call, Mubit asks your provider model the call again for the comparison.

Requests lists the spot-check copies when Include copies is on. See Calls an adapter answers.

Your provider doesn't answer a call an adapter answers, and doesn't bill it, except for the spot-check copies and silent-test references above.

What runs on Mubit's accounts

These run on Mubit's own accounts, never on your provider key:

  • the automatic rating of your calls;
  • training;
  • the exam, and its automatic grader;
  • the decision whether a call goes to an adapter;
  • the adapter's replies;
  • Try models, within its daily limits.

Mubit's own charges depend on your plan. This page doesn't list prices.

Where call content goes

Mubit uses the content of your recorded calls to train and test your adapters:

  • Rating. An automatic rater, a model service Mubit uses, reads each rated call's request and reply.
  • Training. Mubit trains a task's adapter on the task's kept examples, on Mubit's training capacity. An adapter is trained on one project's calls and answers calls of that project only.
  • The exam. An automatic grader, a model service Mubit uses, reads the exam's conversations, your provider model's replies and the version's replies.
  • Routing decisions. For a call that could go to an adapter, Mubit asks a model service it uses whether the call fits the task. It sends the first 2,000 characters of the call's instructions and of its last user message, and up to 3 example user messages from each of your project's tasks it compares the call with.
  • Silent tests and spot checks. Mubit sends copies of calls to the version under test, and to your provider on your provider key.

So the content of your calls reaches model services Mubit uses, as well as your own provider.

A call that Mubit doesn't record in full, sent with x-middleware-record: metadata or off or with x-middleware-store: false, is kept out of all of this: it isn't rated, trains nothing, and is never sent to an adapter or for a routing decision.

ℹ️Note

To keep a whole task's calls on your provider, an admin selects Switch off… on the adapter's page. This stops adapters answering, not rating or training. See Keep calls on your provider.

Next