Cloud models
The catalog
See the catalog
terminal
curl -s https://api.conifer.build/v1/models \
-H "Authorization: Bearer $CONIFER_API_KEY" | jq '.data[] | {id, context_window, pricing}'The response is the source of truth, prices included.
Reading an entry
| Field | What it tells you |
|---|---|
id | The exact string you put in a request's model field. |
provider | Whose model it is. Conifer's own models say conifer. |
context_window | The input budget. Requests beyond it are refused, not truncated. |
caps | Declared capabilities. Check for tools before wiring an agent. |
pricing | Per-million-token rates as exact decimal strings: input, output, cache read, cache write. |
The same data, rendered for reading, is /pricing on the website.
Conifer’s own models
conifer-swift, conifer-grove, conifer-summit, sibelius, silvanus, and the other conifer ids are served like any hosted model: a catalog id, a posted price, and the usual receipt. Check caps before agent use; several are chat-focused.
Which model to use
conifer-swift is the low-latency starting point, and escalating to a frontier id is one string swap. A concrete id is exact. To let Conifer choose, select a saved route (or a reach preset in the CLI) and let the production router admit one physical model.