Setting spend controls

Budgets, alerts, and hard caps for teams, members, and agents — set before the spend happens, not discovered after the invoice.

Relixr gives you spend controls at three levels: the workspace, a member, and a key. Which one you use depends on who — or what — you're capping.

Workspace-level limits

Daily, weekly, or monthly spend caps that apply across the whole workspace. This is the backstop: even if every other control is misconfigured, the workspace cap is the ceiling nothing crosses. Set under Guardrails → Rate Limits.

Per-member limits

A monthly credit cap scoped to one workspace member — useful when several people share a workspace and you want to bound any one person's usage without splitting into separate workspaces. Set from the workspace's member settings; the cap merges into the workspace's policy and takes effect on the member's next request.

Per-key limits

The finest-grained control, and the one to use for agents and automation. A key's spend ceiling is set at creation (see API key scopes) and enforced independently of the workspace total — an agent hitting its own cap doesn't affect anyone else's budget, and a workspace-wide cap being reached doesn't require you to have pre-allocated per-agent limits in advance.

Alerts before hard stops

Budget alerts fire at 50%, 80%, and 100% of a balance or spend cap, by email, before a request actually gets rejected. Use these as your early warning — by the time a request is hard-blocked with 402 insufficient_balance (see Errors), whatever depended on that request has already failed.

Putting it together

• Solo developer: a workspace cap is enough — see Relixr for solo developers.
• A team sharing a workspace: workspace cap plus per-member limits for anyone whose usage needs its own ceiling.
• Running agents: per-key caps as the primary control, set at the same time you scope the key — see Agent fleet on Relixr.