What is Fusebox?
Fusebox helps OpenAI API users set a monthly spending ceiling and get email alerts as their usage reaches set portions of that limit. It uses an API key with only the api.usage.read scope, and checks that the key works before storing it. The tool is for people who want an early warning about OpenAI API spending, including when unexpected usage could come from a retry loop or a leaked key.
Fusebox Features:
Monthly Spend Ceiling: Set a dollar ceiling for monthly OpenAI API spending so alerts are tied to a limit you choose.
Threshold Emails: Receive email warnings when usage reaches 50% and 80% of the monthly ceiling.
Ceiling Alert: Get an email when usage reaches 100% of the monthly spending limit.
Read-Only Key: Connect with an API key granted only the api.usage.read scope, leaving other scopes unchecked.
Key Check: Fusebox checks whether the API key works before storing it.
Quick Setup: Start by entering three fields, with setup described as taking about two minutes.
Ongoing Months: Use the service across unlimited months rather than being limited to a set number of months.
Fusebox Benefits:
Earlier Response: Warnings at 50% and 80% give you a chance to look into rising usage before it reaches your full monthly limit.
Fewer Cost Surprises: A ceiling and email alerts can make unexpected API spending less likely to go unnoticed until it becomes a larger bill.
Focused Access: Using only the usage-reading scope avoids granting the connected key the other listed permissions.
Simple Start: A short setup flow makes it easier to put a spending alert in place without a lengthy configuration process.
Continued Monitoring: Unlimited months let you keep using the same service for ongoing monthly spending checks.
Use Cases:
Side Project Spending: Set a monthly limit for an OpenAI API side project where a modest expected bill could grow unexpectedly.
Retry Loop Checks: Watch for rising API usage when an application retry loop may be sending more requests than intended.
Leaked Key Response: Use the spending alerts as an early signal to investigate unexpected usage that could follow a leaked API key.
Usage Budgeting: Choose a monthly dollar ceiling when you want OpenAI API usage to stay within a defined spending limit.
Admin Key Setup: Connect an OpenAI API organization key with the usage-reading permission while leaving member, project, and API-key scopes unchecked.