Skip to main content

Unified Access Budgets

Budget policies let you cap Unified Access spend before requests reserve wallet funds.

Budget windows​

You can combine multiple windows in a single policy:

  • Hourly — short-term burst control
  • Daily — team or workspace spend guardrail
  • Weekly — shared runway for recurring usage
  • Monthly — invoice and cost-center control

If multiple policies match, the most restrictive effective limit applies.

Policy design tips​

  • Start with monthly org-wide limits, then layer stricter team or service-user budgets.
  • Pair access policies with budget policies so only approved users can consume the most expensive models.
  • Use simulation and effective-budget endpoints before enabling enforcement on production traffic.

Wallet funding order​

Unified Access funding is evaluated in this order:

  1. Monthly seat credits
  2. Wallet balance
  3. Auto top-up (if configured and allowed)

If no funding source can cover the reservation, the request is rejected before it reaches the model provider.

Auto top-up​

Auto top-up keeps wallets healthy without manual intervention:

  • Triggered when balance falls below the configured threshold
  • Enforced with cooldown and daily-cap controls
  • Logged in auto-topup history for audit and finance review
  1. Create read-only dashboards for budget and auto-topup history.
  2. Apply alerting on repeated near-limit events.
  3. Roll out stricter windows to high-cost model groups after observing traffic patterns.