oz0 model provenance

Usage and flags for oz0 model provenance.

For: Operators and developers looking up a command.

Show a model's provenance: what it is reached through (a built-in provider, a preset, an endpoint of the tenant's own, a local model server), who published it, where it came from, the model it was edited from, the digest its nodes report and whether they confirmed it against a pin, and its vetting: who, when, why. Without a model it lists the models the tenant's agents may run on and those it vetted.

A model behind a built-in provider or a shipped preset counts as vetted. A local model, and a model behind an endpoint with a base URL of the tenant's own, is unvetted until a tenant admin vets it: a job that may run on an unvetted model starts tainted, so each call that can send data out waits for a person, and it runs on a node with sandbox tier 1 only. It is never refused for its model.

A vetting is a person's judgement with a reason, not a scan of the weights, and never says a model is safe.

Usage

oz0 model provenance [<provider>/<model>] [flags]

Flags

FlagTypeDefaultDescription
--jsonboolprint JSON instead of a table
--tenantstringdefaulttenant whose models to show
--unvettedboollist only the models that are not vetted

Inherited flags

FlagTypeDefaultDescription
--contextstring$OZ0_CONTEXT or <config dir>/orchestrator-zero/context.jsonCLI context file written by server init
--log-levelstringinfolog level: debug, info, warn or error

See all oz0 commands and the global flags.

On this page
Copyright © 2026