Models

/dashboard/models is a rate card that knows which account is reading it. It sits in Operate, directly under API Keys, because those two are the same sentence in two halves: here is your credential, and here is what it can reach. It reports nothing about your traffic — that is Usage — so it is not a Monitor surface.

Every figure is derived on the server from the registry the router and the meter both read. There is no separate catalogue behind this page and nothing here is fetched from a provider, so it cannot disagree with Models & providers or with the price on a response.

The rates are what you pay, not what we pay

The registry stores the provider's list price. Every rate on this surface is that figure times 1.5 — the published Lobstack rate, and the same arithmetic that produces x-lobstack-cost-usd on a managed request. What the provider charged us is a separate ledger column and appears nowhere in the Console. The list prices were last checked against the providers' own pages on 2026-10-16, and the page says so under its title.

A rate is never rounded into a shorter number. A per-million figure under a dollar is drawn to three decimals rather than collapsed to <$0.01, because a rate card that cannot tell $0.075 from $0.94 is not a rate card. Where the registry holds no usable price the cell is an em dash, never $0.00 — the same rule the ledger applies to cost_usd: null.

What auto serves

Five cards across the top, one per tier, each naming the complexity score it accepts and the model an "auto" request lands on there. This is the routing ladder rendered against your plan, not a second copy of it.

Two labels appear on a tier card and only when they apply, because a row of five cards each saying “within your plan” is five cards saying nothing. Above your plan marks a tier your ceiling excludes. Preference points at a previous-generation key marks a tier whose first choice is a back-compat key rather than a current one — that is a catalogue fault worth seeing rather than hiding, and it is the exact failure that once left auto serving no current-generation model for six weeks.

What your plan reaches

Under the tier cards, one strip states how many of the 18 current keys this account may call. Free is capped at standard; every paid plan reaches flagship. A plan that already reaches everything says so and sells nothing.

A named model above the ceiling is refused, and auto never routes there. Plans that sell top-ups carry the same buy control the allowance panel on Usage does, because “this model is out of reach” and “buy more allowance” are the two things a reader wants at that moment.

The catalogue

Below the strip, the current generation grouped by tier, highest first, filtered by a provider control in the title row. Each card carries the model's label and key, its context window, its provider and — when the two differ — the provider-native id that actually goes on the wire. Underneath: the input and output rate per million tokens, and a button that copies a real request with that key already named.

curl https://www.lobstack.ai/api/gateway/v1/chat/completions \
  -H "Authorization: Bearer $LOBSTACK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-sonnet-5",
    "messages": [{ "role": "user", "content": "Say hello." }]
  }'

The pills

Five, and every one is a fact the registry actually records with a consequence a caller can act on.

What this surface deliberately does not show

The registry records provider, tier, context window and price. It does not record modality, tool calling, structured output or reasoning, so nothing here renders a capability badge — a badge that is wrong is worse than one that is absent, because somebody ships against it.