Models is the console's curated catalogue of the AI models client companies and their API keys can use. Company users browse it as their model menu, described on Models; DataMind staff open the same area with the editing controls. Use this page when you add a model, change what clients see about one, move the two house aliases, or take a model out of service.
The editing view is a DataMind staff area. It appears to DataMind staff accounts; company accounts cannot open it or change the catalogue.
The list shows one card per model, in your catalogue order. A card carries the model's label and upstream ID, the description clients see, its badges and its category:
The status filters All, Enabled and Disabled, and the search box, narrow the list. An empty catalogue reads No models in the catalog yet. and offers Add first model; a search with no matches reads No models match your search. A card with a price snapshot shows its USD per 1M figures (in, out, cache).
A new row joins at the end of the catalogue order and starts enabled. Unless you tick List for clients, it stays out of client menus. Its upstream ID is fixed from the moment it is saved.
Only models from the zero-retention text-model listing can join the catalogue. A model outside that listing is refused: Model "<upstream id>" is not in OpenRouter's ZDR text-output listing - only zero-data-retention models that output text are allowed. A redirect entry, whose ID starts with ~, is refused too, and a model that is already in the catalogue is refused with Model "<upstream id>" is already in the catalog.
The upstream ID is not editable: to point at a different model, add a new row and retire the old one. Capability details (context window, tools, thinking, structured output) are not typed in; they come from the upstream listing and refresh with it.
Closing the dialog with unsaved edits asks Discard unsaved changes?; Discard closes it without saving.
The card menu holds the lifecycle actions. There is no delete: disabling is how a model leaves service, and the row stays.
Unlist {name}?: "Unlisted models leave the client model menus and direct pay-as-you-go requests to them are refused. House aliases are unaffected." List for clients puts it back: "Listed models appear in the client model menus and can be requested directly as pay-as-you-go."Disable {name}?: "Disabled models leave the proxy menu until re-enabled. House-model backings (default or standard) cannot be disabled." Enable asks Enable {name}?: "Enabled models are published to the proxy catalog for API clients."A house-model backing cannot be disabled while it carries a designation; the refusal is Cannot disable a house-model backing - promote another model to that designation first. Promote a successor first, then disable the old row. If the list was out of date when you acted, the refusal is Model not found; reopen the catalogue and try again.
Enabling a model rechecks it against the live upstream listing, so a stale row is revalidated at that moment. When the listing drops a model that is in the catalogue, the platform disables it automatically, and it stays disabled even after the model is listed again until you enable it from its card. House-model backings are never disabled this way: a backing that drops out of the listing needs a promoted successor. The listing side itself, region by region, is tracked on Upstream usage and reconciliation.
Set premium and Set standard on the card menu decide which model backs the two house aliases:
Make {name} the premium default?: "The kartlos-premium alias will point at this model. It must be EU-eligible." Confirm with Set premium; the toast reads Premium model updated.Make {name} the standard default?: "The kartlos-standard alias will point at this model. It must be EU-eligible." Confirm with Set standard; the toast reads Standard default updated.The checks behind the confirmation: the model must be enabled (Only an enabled model can back a house model), must be servable in the EU (A house-model backing must be EU-eligible - any company may be EU-routed and the alias must resolve for it) and must support tool calling (A house-model backing must support tool calling - subscription clients attach tools to chat requests and a tool-less backing cannot serve them). Promoting replaces the current backing, and one model may hold both designations.
Clients never see which model backs an alias: they see kartlos-premium and kartlos-standard. Rows that the platform added itself, rather than through this page, cannot be listed for clients.
Effort curation advertises only the effort levels DataMind has validated for the model: "Advertise only the efforts DataMind validated for this model - the proxy rejects everything else." Tick the levels clients may send; the seven levels are max, xhigh, high, medium, low, minimal and none. Leave every level unselected to advertise the upstream list and pass efforts through unvalidated. Clearing the boxes removes the curation.
none is controlled by the Allow turning reasoning off switch, so clients can send effort none and disable reasoning on this model. On a model whose reasoning cannot be switched off, the switch is off with the note "Unavailable - reasoning is mandatory on this model upstream."Drag a card to change its place in the order; the change saves as you drop it, with Saving… shown while it runs. Reordering is unavailable while a search or status filter is active, and the list says Clear filters to reorder models; otherwise it hints Drag a card to change catalog order. If a save fails, the list returns to the last saved order and the toast reads Reorder failed.
From an enabled card, Show providers opens the provider panel with region tabs Global and EU:
| Column | Shows |
|---|---|
| Provider | The provider that serves the model. |
| Input $/1M, Output $/1M, Cache read $/1M | Each price as base, client and margin: the provider's own price, the sell price a client pays, and the difference. |
| Discount | The provider's discount, when one runs. |
| Uptime, Context, Max output | Availability and the endpoint's token limits. |
| Latency, Throughput | Speed, shown when the provider reports it. |
The panel shows Scanned {date} for its last refresh, or Never scanned; a region with no endpoints reads No endpoints in this region. If it cannot load, Retry re-reads it. The cost and margin figures stay on this panel: client menus show their own provider table without them.
One of a few reasons. The model is not in the zero-retention text-model listing, so it is refused with the listing message in Add a model. Its ID may be a redirect entry that starts with ~: those are refused with Redirect models ("~" ids) are not allowed - their backing and price change upstream, so a billing snapshot for one is stale by construction. Or the model may already be in the catalogue, refused with Model "<upstream id>" is already in the catalog, or be a row the platform added itself, which is not created through this page.
The platform disables it on its next check, so it leaves the model menu and stops serving. The disable is one-way: if the model returns to the listing, it stays disabled until you enable it again from its card. House-model backings are handled differently: they are never disabled automatically, and a backing that drops out of the listing needs a promoted successor.
It is a house-model backing: it is the model behind kartlos-premium or kartlos-standard. The refusal is Cannot disable a house-model backing - promote another model to that designation first. Move the designation to a successor with Set premium or Set standard, then disable this row.
The model must be enabled: a disabled row is refused with Only an enabled model can back a house model. It must also be servable in the EU and support tool calling, because any company may be routed to the EU and subscription clients attach tools to their requests. If it fails either check, pick another model.
Unlisting closes the model to client menus and direct pay-as-you-go requests while a house alias pointing at it is unaffected. Disabling takes it out of the model menu entirely. Both are reversible, and neither deletes the row.
No. Disabling is the lifecycle: the row stays in the catalogue with a Disabled badge and can be enabled again when the model should serve.
No. A row's upstream ID is fixed when it is created. Add a new row for the new model, list or promote it, and disable the old row.
The model has no reasoning support upstream, so there are no effort levels to curate and the card shows No thinking. When the model gains reasoning support, its row picks it up and the editor appears.
Reordering is off while a search or status filter is active: the list shows Clear filters to reorder models, and drag is re-enabled once the list is unfiltered. If no filter is active and the order still snapped back, the save failed; the toast reads Reorder failed and the list keeps the last saved order.
On a providers row: base is the provider's own price, client is the sell price a client pays, and margin is the difference. These figures are for DataMind staff only; clients see sell prices on their own provider table.
Yes. The client model menu and the API model list come from the same catalogue, so a save updates them together; there is nothing separate to publish.