API-key specific rate and spending limits would be good

[_j]

OpenAI doesn’t take feedback articulated clearly, and removed the obviously useful monthly budget hard limit that used to exist for projects and replaced it with illusion.

One can only think that they deliberately enjoy additional profit from overages, abuse, and lack of management interface, just as they enjoy expiring your credits.

@_j

A project, being a stupid overloaded name for a rights sub-container in an authentication domain, makes you think that you could could give a certain amount of credit there dedicated to a project. But no: again, amount of resetting monthly usage to just get an email if exceeded.

• There needs to be a lifetime spend limit on a project, a hard cap with tracking shown, that if set, immediately turns off usage until you increase the dollar figure further.
• There needs to a more granular limit (that works) for recurring usage, that shuts off an application’s project for its day or week budget, detecting and limiting abuse over a maximum. The rate limiter already stops and breaks apps on many model’s requests per day rate limit; this should be the developer’s choice in dollars.
• API key revocation shall collect a “reason” field, and report it in 403 API error messages (“you are fired”)

You can use a daemon loop of monitoring the admin endpoint usage by daily buckets for a project, and then have hooks to delete all the API keys for unusual use - as long as that also stays working.