Skip to main content
Open Settings → Billing in the intended organization. Organization members can view Usage; organization Owners have overview and budget management controls. Price administration is a separate platform-administrator function. Available sections depend on your role and the deployment’s cost services.

​
Inspect spending

Open Usage, select the period and available grouping, and inspect the currency, provider and allocation information alongside the total. The overview’s month-to-date period uses the current UTC month. A provider’s reported cost, a runtime token estimate and a project allocation are different measures; do not add overlapping figures together. Refresh before investigating a new change. Missing, stale or unallocated provider data limits what the totals establish; it is not evidence of zero spend. Review source status before reporting a project total. The agent cost guidance and Lakehouse cost guidance explain these measures.

​
Set a project LLM budget

An organization Owner can open Billing → Budgets:
  1. Choose New budget, select the Project, and enter the Monthly LLM budget and Currency.
  2. Decide whether to enable Stop new LLM usage when this budget is reached. Review the effect with the project’s users before changing it.
  3. Choose Save budget, then check the saved amount, currency and status. Use Edit budget beside an existing project to change it.
For example, if your team has agreed a monthly test limit of 100 in USD, enter those values and verify the saved budget. This is an input example, not a recommended spend limit. With the stop option enabled, an in-flight response may finish and a subsequent model call can be blocked. Without it, usage continues after alerts. This budget covers AgentOps LLM usage; it is not a cap on every cloud charge. Projects without a project budget are shown as unlimited, though an organization-level protection policy can still apply.

​
Review organization protection

The budget view also has an organization Enabled setting, Monthly limit, Currency and Save control. Review the affected projects, save deliberately, and check the resulting policy state. An organization limit and each project allocation need not describe the same amount. If a source is stale or a policy cannot be loaded, inspect the error with the administrator responsible for billing. A client update does not configure provider access or reset an exhausted budget.