Providers and overrides

The Providers page in the MultiRoute app shows the default configuration for providers and models. You can use it as-is (read-only) or create your own configuration that overrides the default. Overrides are stored in a config with parent_id set to the default config—you never modify the global default.

Default config vs your config

Default config — A global, read-only configuration that defines which providers and models are available. You cannot delete or disable providers in the default; it is shared and managed by the product.
Your config (override) — A config with parent_id = default_config_id. It inherits the default's providers and models. You can add providers, override API keys or models, and disable providers from the default (for your config only). Disabling is an override in your config that marks a provider as disabled—it does not change the default for anyone else.

How the Providers page works

If the default config is not found (e.g. not yet set up) — You see a single Create config button. Creating builds your override config (with parent_id = default_config_id and empty overrides). Once the default exists, you'll see the normal Providers view.
If you already have an override — The app loads that config and shows the effective list (default merged with your overrides). You can add providers, edit overrides, disable/enable providers from the default, and remove providers you added.
If you don't have an override yet — The app shows the default config in read-only mode. Use Create my configuration to create your override; after that, all edits apply to your config.

Any change while viewing the default (e.g. add provider, edit API key, disable provider) creates your override config with that change and then switches to editing that config.

What you can do in your config

Add providers — Add new providers or OpenAI-compatible endpoints.
Override API key or models — For a provider that exists in the default, set your own API key or model list.
Disable a provider — For a provider that comes from the default, add an override with disabled: true. That provider is then disabled in your effective config only; the default is unchanged. You can enable it again by removing the override or setting disabled: false.
Remove a provider — You can only remove providers that you added (not those that come from the default). Providers from the default can only be disabled, not deleted.

Inheritance in plain terms

Your config inherits from the default. Only your additions or overrides are stored (e.g. "this API key for OpenAI", "disable provider X", "add this custom endpoint").
The system merges the default with your overrides to produce the effective list of providers and models. API keys and model lists from your overrides take precedence; otherwise the default's values are used.

Managing via the app and API

Providers page — In the app sidebar, open Providers to view the default or your merged config, create your configuration, and add or override providers (including disable/enable).
Config API — Use the config API for programmatic access: list configs, get a config by ID, create a config (with optional parent_id), and update or delete your own configs. When creating an API key, you choose which config that key uses.