The problem
LIA keeps a catalogue of all the models she knows how to use: several dozen models, each with its capabilities (context size, tools, images, reasoning) and its price. This catalogue is used to bill accurately and to offer only settings that work.
The administration screen offered one window per model. That's perfect for fixing a price. It gets painful when a provider revises its whole price list and you have to open thirty windows one after another, without being able to compare the rows.
What I wanted
I wanted the administrator to be able to export the catalogue to an Excel workbook, edit it at leisure with its filters and formulas, then reimport it. And I wanted a mishandled file to be unable to damage the catalogue: a spreadsheet is a powerful tool, and an error spreads quickly in it.
How it works
From the LLM Pricing screen, the export produces a workbook with instructions in your language, one row per model, a tab for time-of-day pricing and drop-down lists for the possible values. You edit, you reimport, and the import happens in two steps:
- The preview. LIA reads the file and shows you, field by field, what's going to change. Nothing is written yet. An unreadable cell is flagged precisely, so you know what to fix.
- Applying. LIA recomputes the plan and refuses if it differs from the one you reviewed: what you approved is exactly what gets written. If a colleague has changed a model since your export, the preview points you to that exact row: you know what to review, and nothing is written from an outdated state.
A few rules make the file safe:
- Columns recognized by their key. Each column carries a hidden key, whatever its position. You can reorder them, hide some, add some, or export in French and reimport in German.
- Nothing is deleted silently. A row missing from the file deletes nothing: a forgotten filter can't empty the catalogue. To remove a model, you set its “active” column to false, and setting it back to true reactivates it.
- All or nothing. At the slightest unresolved anomaly, nothing is written.
- What hasn't changed isn't rewritten. Otherwise, every import would create a new version of every price, and the price history, which tells you what a given month cost, would fill up with noise.
The file says what is
Some columns are computed and read-only, because the raw data would be misleading. A model with no active price would be billed at zero: the file spells it out in full. An off-peak price appears on the row that carries the price, where you can see it. And the workbook carries a format number: a file in an old format is refused, so it isn't misread.
Each model has only one price in force at a time, and the database guarantees it. So the file's row states a single price, and no tool has to pick one among several.
The limits
- For now, only the catalogue of models and their prices can be exported this way. The mechanism is generic: extending it to another screen means describing its columns, not rewriting the format handling.
- It's reserved for the instance's administrators.
- An Excel workbook is actually a compressed archive. So the file is capped in size and checked before being decompressed, like any archive received.
Read more: Tuning LIA's models without a restart, and without impossible configurations.
