Skip to main content

​
crewship model list

Lists the models a provider can serve.
Two sources, and auto picks between them. For a provider the server can answer for — anthropic, openai, google, ollama — the list comes from the server: live from the provider when the workspace has an active API key, a curated fallback otherwise, and the source field says which. That path needs a login and a workspace. Every other provider is answered from the snapshot compiled into the binary, with no token, no workspace and no server, which is how the providers this build has no codec for are still visible and priced.
Rows are in source order — most-capable and most-recent first, the order both the curated lists and the catalog use — not alphabetical.
The rates in this table are the catalog’s, not necessarily the billed ones. Paymaster’s hand-verified table sits above the snapshot and can correct it, and a long-context model is billed at its ceiling. Ask crewship model price for the number that will actually reach the ledger.
--source live forces the server path for a provider auto would have answered offline; --source catalog is the escape hatch when the server is unreachable or refuses a provider id. A model the snapshot has never heard of — an Ollama tag, or a release newer than the fetch date — simply carries no catalog columns.

​
crewship model price

Prints the per-million-token rates paymaster will bill a (provider, model) pair at, which of the five lookup steps produced them, and the cost of a call with the given token counts. Entirely local: the rate card and the catalog are compiled in.
The four channels are priced separately, which is why --in excludes --cached rather than including it. That is the same convention the ledger uses — see Paymaster.
rate source is the reason the command exists:
none is a finding, not a price. It means no step of the lookup had an opinion, so the call bills $0 — almost always a typo in the provider id, or a Provider.Name() nobody added a ceiling row for. Every provider the registry or the catalog knows has one, so none should never appear for a provider you actually configured.A genuinely free local runtime reads wildcard, not none: ollama/* and local/* are $0 rows someone wrote deliberately. The two used to be indistinguishable and both reported free, which meant a typo’d vendor was presented as a free local model.A fallback is the opposite failure and just as misleading if taken at face value: openrouter’s ceiling is $150/Mtok input, because a gateway reselling 353 models has no median worth guessing at. Reading a ceiling — or a $0 — as a real price is how a budget line stops being believed.
The catalog says line appears when the snapshot also carries the pair, so you can see the two sources disagreeing before an invoice does — it is the snapshot’s ceiling for that model, the same number the catalog step would have billed, which is why it can sit well above the table rate that shadows it. The unknown <provider> model bills at line is what that provider charges for a model nothing prices, printed to give the resolved number a scale to be read against.