The request path
Every call carries atask. The label decides which route serves it, and the
same label files the trace under that task. A task with no approved route yet
falls through to your default model, so labelling is always safe to add.
What a task accumulates
Each step is worth something on its own. Measurement alone usually reshuffles what a team thinks is expensive. Most tasks stop at Routed down, because an existing cheaper model turns out to be good enough once someone defines what good means.Why a route is never promoted on price
Price only breaks ties among candidates that already pass. Without a contract on a workload there is nothing to gate on, so it stays on the model you name rather than guessing. Nothing reaches production traffic without a human accepting it, and every promotion is versioned and reversible.What you manage, and what we do
Managed only for now. There is no bring-your-own-key or self-hosted option, so
there are no provider accounts to configure and no upstream credentials to
pass through.
Quickstart
First labelled call in four steps.
Tasks
Naming and granularity, the part that decides whether any of this works.