Usage

Settings → Usage shows the current billing cycle’s consumption on four axes, each against the workspace’s enterprise license — seats, included quantities, and monthly ceiling are granted by Nora when the license is issued. Metering is per workspace and real-time; the month picker steps through past cycles.

​

The four axes

• Runs — agent runs plus foundry runs.
• Memory — storage the agents accumulate, in GB·month.
• Knowledge — library storage. Knowledge-graph and vector operations are not billed.
• Verify & improve — tokens used by the loop’s own model. Failure analysis, simulation, and improvement run on this budget; improvement itself is free of charge.

Each axis shows usage vs. the license’s included quantity, the overage unit price, and this cycle’s overage charge. Each axis also has an editable dollar cap (Your cap · alert at the limit). Below the axes, Total overage cap bounds the cycle’s total overage (up to the license’s monthly ceiling); Save caps applies the numbers. Crossing a cap alerts the owners; usage keeps being recorded — enforcement is at the license’s monthly ceiling, not at the self-imposed cap.

​

Cost alert thresholds

Owners get an email when the cycle’s spend crosses each threshold: 50%, 80%, 100% of the monthly ceiling by default. Enter your own as comma-separated percentages (1–100) and Save thresholds. Alerts go to the account email, so email verification must be completed for them to arrive; the page offers Resend verification if yours isn’t.

​

License terms

The License header on the page shows the contract’s term, seat count, contract currency, and monthly ceiling. Statements are always denominated in USD (the rate card is USD); the contract currency is recorded alongside so the finance team converts at the rate the contract specifies when raising the KRW / EUR / … invoice. Existing workspaces from before the enterprise-only switch are grandfathered — their prior ceiling stays in place; contact us to lift it.

​

Related