oz0 usage export

Exports a tenant's metered usage recorded from --from up to --to.

For: Operators and developers looking up a command.

Exports a tenant's metered usage recorded from --from up to --to. These are UTC days by the database's clock when management took each row; --to is the day after the last.

The stable schema has one row per model call or plugin report and unit kind (input, output, cache read and cache write tokens, web searches, compute seconds, a plugin's units), and per day of outside spend. Each row includes:

  • A row ID that is the same in every export, and the schema version.
  • The provider, model and region; the tenant, its team and tags; the job and agent.
  • The quantity, list cost, effective cost and currency.
  • The source, the pool member that served a call and the plugin whose tool asked for it.

Exporting a period that has passed again gives the same rows. Rows written before the export's attributes were recorded leave region, team, tags and list cost empty rather than guess them. Under works-council mode a team shows only where its figures may be shown; no column names a person. The tenant's admins may; --all-tenants needs a cluster admin. Each export is audited.

Usage

oz0 usage export [flags]

Flags

FlagTypeDefaultDescription
--all-tenantsboolevery tenant (cluster admins)
--formatstringcsvcsv or jsonl
--fromstringthe first UTC day, such as 2026-10-01
--outstringwrite to this file instead of standard output (created with mode 0600)
--tenantstringdefaulttenant
--timeoutduration1h0m0sgive up when the whole export takes longer than this (0 for no limit)
--tostringthe day after the last, such as 2026-11-01 (at most 400 days after --from)

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