Choosing a model

The picker above the input lists every available model. Every row carries the same two numbers.

Every row shows

Price
per million tokens
Context
length

Switch mid-conversation and the thread comes with you.

Kinds

Three kinds worth telling apart

Works at a zero balance

Free models

They cost nothing when available to your account. The picker shows which models you can use, their prices and context lengths.

Costs more

Reasoning models

They think before answering. Worth it on hard problems, not on simple ones.

Longer context

Long-context models

They matter when you paste a big file or work a long thread.

Where the catalogue has them, a row also shows a class label (a rough family tag) and a concurrency cost: how many of the shared inference slots one request to that model uses. Heavier models use more, which is why they can hit a busy limit sooner under load.

Full catalogue

Recommended picks, or search everything

The picker defaults to a short, recommended list. Switch to All Featherless models to search the complete catalogue instead (tens of thousands of models). Keep scrolling with Load more for further results.

ZeroLog keeps the previous model list when an incomplete Featherless catalogue would hide many models. Small retirements and returning models still update normally.

For more control, open Models in the navigation. The same toggle is there, plus filters for class and minimum context, sort by newest, price, context, or name, and category tags (chat, tools, vision, reasoning, code, long context, free) so you can spot what a model is built for at a glance.

In practice

Cheap to explore, strong for the hard step

One pattern that holds up:

  1. 01

    Cheap model to explore.

  2. Switch 02

    Strong model for the hard step.

  3. Switch back 03

    Cheap again to tidy up.

If a model fails

When the model you picked cannot answer

If the selected model cannot handle a request, the chat shows an error. Check the message, then retry or choose another model shown in your picker.

Malformed request

You see the error; another model may reject it too.

Device tools

The CLI engines (Claude Code and Codex) cannot call the tools of a connected device such as the Android app. The thread says so when it happens.

Availability

Use models shown in your picker

ZeroLog checks model access across chats and automated features. Agents, Ultracode, automatic model choice and usage limits use models available to your account.

When you explicitly request a model that is not available to you, ZeroLog returns model_not_available. Choose a model from your picker and try again.

Featherless models are available to existing accounts. See Model availability for the current access policy and the earlier pause.

Providers sometimes retire models, so the list and prices in your picker can change. In ZeroLog Code, a saved model choice that has been retired may be routed to a replacement. The response identifies both models and includes a notice, whether it streams or arrives all at once. Choose a current model in the picker to set a different one.

Price

What the quoted price already includes

On ZeroLog credit

Every price you see already includes the 2% service margin, so what is quoted is what is charged.

On your own key

Usage on your own API key carries no margin at all, because that money never passes through here.

Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Security · Status · X · Legal & privacy · Home