Per API-Key Usage Cap

🎯 What is it?

Admins can now set a spending limit on individual API keys. Each key can have its own maximum dollar amount for API usage, calculated on a 30-day rolling basis. This gives you precise control over how much each API integration or user can spend.

💡 Why is it useful?

As your team scales and more people use Dust programmatically, it becomes harder to track and control costs at a granular level. Until now, your only option was a workspace-wide limit. This new feature helps you prevent budget overruns, test new integrations safely, and allocate resources more strategically across different projects or teams.

⚙️ How does it work?

Simply set a dollar cap when creating or editing an API key. Once the key reaches that spending limit within any 30-day period, it will stop working until the rolling window resets. Keys without a cap continue to use the workspace's overall limit.

✨ Concrete Use Cases

Here's how you could use it:

Testing environment: Set a $50 cap on API keys used for development and testing to avoid unexpected costs from runaway scripts or experiments.

Team allocation: Give your marketing team an API key with a $500 monthly cap and your engineering team a separate key with a $2,000 cap, matching each team's actual needs and budget.

Third-party integrations: When connecting Dust to external tools or contractors, set conservative limits to control costs while you evaluate usage patterns.

📈 Benefits for you

Better budget control: Prevent individual integrations or users from consuming your entire workspace credit unexpectedly
Safe experimentation: Test new use cases without risking your full budget
Clearer accountability: Track and manage costs at the team or project level
Flexible scaling: Adjust limits as needs change without affecting your entire workspace

🚀 How to access it?

Admins can access this feature in the Dust workspace settings, under the API Keys section. When creating a new API key or editing an existing one, you'll find the option to set a usage cap. No action is required if you prefer to keep your current setup—API keys without a cap will continue to work as before, limited only by your workspace's overall limit.