Skip to main content

Providers, models, and routes

PreviewAvailable on: WindowsShips in the preview channel only. Not a stable release.

An execution route is eight things, not one. Knowing them is how you control cost and behaviour.

"Which model ran this?" is rarely one question. Harmony treats the full path as an execution route, and most cost and behaviour surprises come from a route element you were not tracking.

The shape of a route

The eight elements of an execution routeAn execution route is a chain of eight elements: harness, provider, account, model, effort, tool set, platform, and billing class. Harmony can observe the harness, provider, platform, and tool set. It cannot observe whether you are authenticated to the account, whether your plan entitles the model, or your remaining quota. Billing class determines whose money is spent.Harmony CAN OBSERVEHarnessthe programProviderthe vendorTool setpermitted callsPlatformwhere it runsHarmony CANNOT OBSERVEAccountauthenticated?Modelentitled?EffortdepthBilling classwhose money is spent, under which plan — shown before consent, or the run blocks
Four elements Harmony resolves itself; three belong to the provider and are invisible to it. Billing class is the consequence of the whole chain.

The eight elements

ElementMeaning
HarnessThe agent program being driven
ProviderThe vendor behind it
AccountWhich of your identities with that provider
ModelThe specific model requested
EffortReasoning depth, where the provider exposes it
Tool setWhat the agent is permitted to call
PlatformWhere the process runs
Billing classWhose money is spent, under which plan

Two steps of the same plan can differ in any of these.

A route displayed before a run is a route you can refuse. This is why orchestration shows the chosen model per step with a stated reason, along with projected cost and billing route.

IMPORTANT

If projected cost or billing route cannot be determined, a run should block rather than proceed. Consent to spend you cannot see is not consent.

What Harmony knows, and what it does not

FactObservable by Harmony?
Provider binary exists and resolvesYes
Detected versionYes
You are authenticatedNo
Your plan tierNo
Remaining quotaNo
Rate-limit stateNo

Harmony does not hold your provider credentials, so it cannot report your login state or entitlements — and it does not guess them. See account and authentication.

Changing the route

In the TUI:

/provider
/model
/profile

Changing route mid-session is legitimate and consequential: later turns in the same transcript can behave differently from earlier ones. When comparing outputs, check the route before concluding the model changed its mind.

Billing

Everything you spend goes to the provider whose plan you used, under that provider's pricing. Harmony is free to use and does not mark up inference. There is no background usage — a turn happens because you started one.

NOTE

"Free" refers to Harmony itself. Your provider subscriptions and API keys are unaffected, and they are what you are actually spending.

Custom providers

If you run an agent CLI that is not in the registry, you can define it yourself. The registry is a list of providers Harmony knows how to launch, not a limit on what it can launch.

The generated list of recognised ids is at provider registry.

Do not treat model rankings as universal

Which model is "best" depends on the task, the repository, and the route. Harmony does not publish anecdotal rankings as fact, and neither should your team's internal docs.