Overview
Bifrost keeps a model datasheet: context windows, token limits, deprecation flags, capability flags (tool calling, structured output, reasoning, …) and base prices for every model it knows. The datasheet is synced from a remote source every 24 hours (see Custom Pricing for the URLs and interval). A sync overwrites every synced value. The Datasheet Editor lets you keep your own values anyway:- Edit any datasheet value: context length, max input and output tokens, deprecation, base prices, capability flags and any other model parameter.
- Add custom models the datasheet does not list, such as a fine-tuned or self-hosted model, so they are priced and described correctly.
- Edits survive updates. Bifrost stores your edits separately and re-applies them after every sync. The synced (upstream) value stays visible next to yours.
- Drift detection. When upstream changes a value you edited, the entry is flagged Upstream changed and shows the value it had when you saved.
Base prices you set here replace the datasheet price wherever Bifrost prices a request from the catalog. Pricing overrides still apply on top, so a virtual-key or provider-key override keeps working against your edited base price. A provider that reports its own
usage.cost above zero is priced from that figure instead, unless ignore_provider_cost is enabled on it; see Providers that report their own cost.How edits are applied
Each edit is a datasheet override for one(provider, model, mode) entry. It holds two JSON merge patches:
In a patch, a key sets the value,
null clears it, and an omitted key leaves the value unchanged by that patch. Mode-wide pricing overrides apply before mode-specific overrides. If both set the same field, removing the mode-specific key exposes the mode-wide value. To restore the upstream datasheet value, remove that field from every applicable override; deleting one override leaves any other applicable overrides in effect.
The model-parameters entry has no mode, so a
params_patch applies to every mode of the model, whichever mode the override targets. When several overrides for the same model carry a params_patch, they apply in order: the mode-wide override first, then the others by mode.Editing an entry
- Web UI
- API
- config.json
- Navigate to Models → Datasheet Editor in the sidebar
- Search for the model, or narrow the list by provider. Turn on Edited only to see the entries you have changed
- Click the edit icon on the row
- Change any field. Empty fields and Follow datasheet choices keep following upstream; the datasheet value is shown under each field
- Click Save
Adding a custom model
A custom entry describes a model the datasheet does not list. Bifrost prices requests to it from your values and reports its limits and capabilities like any other model. If the datasheet later starts listing the same model, your values still win, and the upstream values show up next to them.- Web UI
- API
- config.json
- Navigate to Models → Datasheet Editor
- Click Add custom model
- Pick the provider, enter the model name and choose the mode
- Fill in the limits, prices and capabilities you need
- Click Save
Upstream drift
With a config store, saving an override records the upstream value of every field it patches. After each sync Bifrost compares those baselines with the current upstream values:- In the Web UI the entry gets an Upstream changed badge, and the field shows the value it had when you saved.
- In the API,
drifted_fieldslists the affected fields aspricing.<field>orparams.<field>.
config.json without a config store have no recorded baselines, so later upstream changes cannot be reported.
For a pricing override without mode, Bifrost records and compares the baseline from only the first mode in sort order. Changes confined to other modes do not trigger a pricing drift indication. Use mode-specific overrides when each mode needs its own pricing drift tracking.
Your value keeps applying either way. Repeat the API save with the same patches to accept the new baseline without changing your override. The Web UI only enables Save after a field changes. To switch to the upstream value instead, remove the field from every applicable override and save.
Permissions
With role-based access control (Enterprise), the editor has its own Datasheet resource, so a role can browse models without being able to change their limits or prices.
By default Admin holds both, and Developer and Viewer can only view. Custom roles get no access until you grant it.
In a cluster, a change made on one node is picked up by the others through the same reload that follows a datasheet sync.

