nora billing

Billing surfaces workspace-level financial information from the CLI. Nora is sold as an enterprise license — seats, included quantities, and the monthly ceiling are set when the license is issued. Self-serve payments aren’t part of the product; the CLI reads state and lets you set a self-imposed spending cap.

Commands

Command	Description
`billing state`	Current license snapshot (term, seats, currency, ceiling).
`billing usage`	Per-meter usage for the current billing cycle.
`billing history`	Historical monthly usage.
`billing invoices`	All usage statements ever issued.
`billing set-overage-cap`	Set a self-imposed monthly spending cap (or clear it to the license ceiling).
`billing open`	Print / open the Nora billing settings URL.
`billing set-tax`	Set business tax fields shown on statements.

`billing state`

nora billing state

Prints:

License term (start & end).
Seats and included quantities.
Contract currency (KRW / EUR / …). Statements are USD; the finance team converts at the rate the contract specifies.
Monthly ceiling (the license’s absolute stop).
Self-imposed overage cap (if set).
Overage used this cycle.

Add --json for machine output.

`billing usage`

nora billing usage

Current billing cycle usage broken down by meter. Each meter line shows used vs included (the license’s included quantity) and the overage rate above that.

`billing history`

nora billing history                                    # last 6 months (default)
nora billing history --from 2026-01-01 --to 2026-06-30  # custom range

Monthly usage rollup for cost analysis and forecasting.

`billing invoices`

nora billing invoices

Every usage statement ever issued for this workspace:

Statement number.
Period covered.
Amount (USD).
PDF link.

Add --json for a script-friendly list. Nora doesn’t process card payments — the enterprise contract governs payment terms; statements exist for the finance team.

`billing set-overage-cap`

# Cap at $500/month
nora billing set-overage-cap --cents 50000

# Revert to the license's monthly ceiling
nora billing set-overage-cap --clear

Sets the workspace’s self-imposed monthly spending cap. Values are clamped server-side to the license’s ceiling — the response echoes the effective cap after clamping. Crossing the cap alerts the owners; usage keeps being recorded. Enforcement stops at the license ceiling, not the self-imposed cap.

--cents <n> — cap in cents (USD).
--clear — revert to the license’s monthly ceiling.

Only Owners can change this.

`billing open`

nora billing open                       # print URL to billing settings
nora billing open --section usage       # deep-link to usage
nora billing open --launch              # open in default browser

Prints (or opens) the URL of the workspace’s billing settings page — usage, statements, cap controls. Flags:

--section usage|invoices — which page to link to.
--launch — open in default browser instead of printing.

`billing set-tax`

nora billing set-tax \
  --business-number "123-45-67890" \
  --tax-email billing@yourcompany.com

Sets business tax fields that show on statements.

--business-number — tax registration number (사업자등록번호 for Korean tenants). Pass "" to clear.
--tax-email — email for statement delivery.

Fields are DB-only — no provider-side effect.

Recipes

Set a spending cap in a bootstrap script

nora billing set-overage-cap --cents 20000    # $200/month

Monitor spend

usage_cents=$(nora billing usage --json | jq '.total_cents')
[ "$usage_cents" -gt "50000" ] && echo "Warning: >$500 spend this cycle"

Download all statement PDFs

mkdir -p statements
for stmt in $(nora billing invoices --json | jq -c '.[]'); do
  url=$(echo "$stmt" | jq -r '.pdf_url')
  num=$(echo "$stmt" | jq -r '.number')
  curl -sL "$url" -o "statements/${num}.pdf"
done

Compare usage across workspaces

for ws in acme-dev acme-staging acme-prod; do
  echo "$ws:"
  nora --workspace "$ws" billing usage --json | jq '.total_cents' | \
    awk '{printf "  $%.2f\n", $1/100}'
done

What billing does NOT cover

Provider costs (OpenAI, Anthropic, Google API charges) billed by the providers directly on BYOK. See nora providers.
Storage attached via BYO buckets — you pay your S3 / R2 provider directly.

Nora billing covers the platform layer: workflow execution, trace storage, retrieval infrastructure, memory, and managed services.

Usage — the same numbers rendered in the Settings UI.
nora providers — provider API key management (billed by provider).
Audit trail — billing-related changes are logged.

CLI

SDK

Local App

nora billing

Commands

`billing state`

`billing usage`

`billing history`

`billing invoices`

`billing set-overage-cap`

`billing open`

`billing set-tax`

Recipes

Set a spending cap in a bootstrap script

Monitor spend

Download all statement PDFs

Compare usage across workspaces

What billing does NOT cover

​Commands

​billing state

​billing usage

​billing history

​billing invoices

​billing set-overage-cap

​billing open

​billing set-tax

​Recipes

​Set a spending cap in a bootstrap script

​Monitor spend

​Download all statement PDFs

​Compare usage across workspaces

​What billing does NOT cover

​Related

Commands

`billing state`

`billing usage`

`billing history`

`billing invoices`

`billing set-overage-cap`

`billing open`

`billing set-tax`

Recipes

Set a spending cap in a bootstrap script

Monitor spend

Download all statement PDFs

Compare usage across workspaces

What billing does NOT cover

Related