How Neo picks a model
A look inside the router: level, kind of work, and a fallback for every step.
For every message, Neo asks three quick questions: what kind of work is this — text, code, images, voice? How hard is it? And what level did you choose?
The answers point to a short list of the best models for that cell, in order. If the first one is slow or fails, the next takes over automatically — you just see the answer.
Always measured
Every request is logged with the model, latency and cost, so routing keeps improving from real use — and so you can see exactly where your credits go.
