Hi guys, I am an avid fan of the legacy usage page on OpenAI dashboard and think the new version is a step backwards, because you cannot pull an overall report for all endpoint types but instead have to select them one-by-one.
I need to extract the said report monthly for my own accounting purposes, so I’ve now vibe-coded a simple Streamlit app to generate the legacy-like usage report.
The link to the app is here. The code is also open-sourced and you’ll find the GitHub repo link on the app page.
There might still be issues because I haven’t encountered all possible token type columns so the order of columns might differ from the old report format. Feel free to post issues to my repo if you find any! Thanks
p.s. I forgot to mention, to programmatically access your account via the API, you have to generate yourself an ADMIN API key for your account. It’s different from the normal token API key you use to access models. I recommend generating a READ-ONLY key, as I don’t need to modify anything, just read. You can find the admin API key page here: https://platform.openai.com/settings/organization/admin-keys
Or, since the code is open source, you can just clone the repo and run it all offline for maximum safety.
Says “open source” but there is no source. And a running application doesn’t have to be based on alleged code. “INPUT YOUR ADMIN API KEY HERE”, how about “nope”.
The rights this confers can create more admin keys as fast as you can try to delete them. Invite users to an organization as owner and kick you off. Archive all your projects permanently and delete keys.
You have to only pray that OpenAI hasn’t and won’t ever fail on “read-only” rights, to then have your complete org dumped out anyway.
As I mentioned, you can take the source code and run it offline after thorough audit, for full privacy. I only shared something I feel is useful because I had this need myself. No need to go toxic here, thank you.
(Of course, I used Cursor / Claude 4 combination when vibe-coding so no knowing what the rival AI model has hidden in the code, lol)
What is problematic is the web app offering to consume an administrator API key.
“For you API users who can’t run code or inspect it, can’t interpret the current usage page or make API calls yourself, and if I’m lucky, can’t set up permissions, go ahead and put takeover rights to the entire organization into this box.”
