oz0 provider pool
For: Operators and developers looking up a command.
A pool lists deployments of the same models behind the same wire format, each with its own endpoint, key, region and data-keeping: Azure deployments in several regions or subscriptions, Bedrock in several regions, self-hosted replicas.
The gateway takes each call's reservation once, at the highest price any member may charge, chooses the member with the most headroom by weight (the job's or conversation's last member while it has headroom, where its prompt cache is), and moves a call that gets a 429 or a 5xx before any output to another member, while the first cools down for as long as its answer says. The call is recorded once, naming the member that served it.
Several keys of one OpenAI project or one Anthropic workspace share one limit, so a pool of them adds nothing; where a provider routes for itself (an Azure Global deployment, a Bedrock cross-region inference profile), prefer that. A record with a pool has no base_url of its own; its own key, auth, region and retains-data are what members that name none take.
Usage
oz0 provider pool [command]
Subcommands
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.