Documentation Index
Fetch the complete documentation index at: https://docs.fireworks.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
firectl billing get-usage returns your account’s usage and rated costs for a time range,
grouped by dimensions you choose — deployment, accelerator type, model, region, or custom
team/project/environment tags.
This complements Exporting Billing Metrics: use
export-metrics for a raw per-event CSV dump, and get-usage for a grouped, rated view.
Requires
firectl 1.7.21 or later. Run firectl version, then firectl upgrade if needed.Usage
-o json for machine-readable output.
Examples
Flags
| Flag | Description |
|---|---|
--start-time | Start time (inclusive), as YYYY-MM-DD or 'YYYY-MM-DD hh:mm:ss'. |
--end-time | End time (exclusive), same formats. |
--usage-type | all, serverless, or dedicated-deployment. Defaults to all. |
--group-by | Dimension to group by. Repeatable. |
--filter | key=value filter. Repeatable; repeated values for the same key are OR’ed. |
--timezone | IANA timezone for daily aggregation (e.g. America/Los_Angeles). Defaults to UTC. |
--account-costs-only | Print only account-level cumulative costs for the range. |
-o, --output | text (default) or json. |
Grouping dimensions
Valid--group-by and --filter dimensions depend on the usage type:
- Serverless:
model_name,api_key_id,api_key_name,annotations.team,annotations.project,annotations.environment - Dedicated deployment:
deployment_name,accelerator_type,annotations.team,annotations.project,annotations.environment
placement, e.g. US, EUROPE,
GLOBAL) and metered accelerator_seconds.
Custom tags (team / project / environment)
Group byannotations.team, annotations.project, or annotations.environment to split usage by
your own labels. The tag source depends on usage type:
- Dedicated deployments: set an
annotationsmap on the deployment, e.g.{"team": "search", "project": "x", "environment": "prod"}. - Serverless: send a per-request header, e.g.
Fireworks-Annotations: team=search,project=x,environment=prod.
Granularity
Usage is aggregated into daily buckets (--timezone sets the day boundary). There are no
sub-daily buckets.
See also
- firectl billing get-usage - Command reference
- Exporting Billing Metrics - Raw per-event billing CSV export
- Account quotas - Spending tiers and budget controls