Budget hierarchy
All three are checked independently. A request is blocked if any limit is exceeded.Step 1: Set up team keys
Create one key per developer or team role:Step 2: Configure alerts
Set a webhook alert so you’re notified before budgets run out: Console → Webhooks → Add endpointStep 3: Distribute keys
Send each developer theirwardin_sk_ key. They set it as ANTHROPIC_AUTH_TOKEN (and ANTHROPIC_BASE_URL=https://gw.wardin.ai) in their environment. No other changes to their workflow.
Budget increase requests
Developers can request a budget increase from MY LANE in the dashboard. Requests land in LEDGER, where you can approve, deny, or set an expiry date for temporary increases.- Approved with expiry: The limit is elevated immediately and automatically reverts at the expiry date.
- Approved permanent: The limit is raised and stays until you change it.
- Revoked: You can revoke an approved increase at any time before expiry.
Viewing spend
Overview shows org-wide spend and allocation; LEDGER breaks it down by team and developer. Each developer sees their own sessions with per-session cost under MY LANE. To pull spend data programmatically:Recommended budget levels
| Role | Suggested monthly budget |
|---|---|
| Individual contributor (interactive) | 150 |
| Senior / staff (heavy AI usage) | 300 |
| CI / automation | 500 |
| Tenant ceiling | Sum of key budgets × 1.2 |