oz0 provider
For: Operators and developers looking up a command.
A provider is a record: its base URL, the wire formats it speaks (anthropic-messages, openai-chat, openai-responses), the header its key goes in and the tenant secret that holds the key, prices and capabilities per model, its region and whether it keeps data.
The gateway passes calls through unchanged and never translates between formats. anthropic, openai and local (models on a node's own model servers) are built in; presets for other common providers ship with the server, and a tenant adds any endpoint of its own. A record with --translator is a translation gateway you run yourself, such as agentgateway: its calls are marked lossy.
Besides a key in a header, --auth-kind signs calls with an OAuth2 token the edge gets from a token endpoint (oauth2_client_credentials, oauth2_jwt_bearer) or with AWS SigV4 (sigv4); the presets vertex, azure-openai-entra, azure-foundry-entra and bedrock use them. --auth-kind federated stores no key at all: the edge exchanges the calling agent's own token from the tenant's issuer at the cloud (--cloud aws, gcp or entra), as the presets bedrock-federated, vertex-federated, azure-openai-federated and azure-foundry-federated do.
Usage
oz0 provider [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.