npx @ai-assist/openai-apilyzer -h
Usage: openai-apilyzer [options]
Options:
--authorization <authorization> authorization token
--organization <organization> organization id
--start [start] start date, default is 30 days ago (default: "2023-03-14")
--end [end] end date, default is today (default: "2023-04-13")
--format [format] json/csv format of output, default is json (default: "csv")
--output [output] output file, default is openai-api-usage-{options.start}-{options.end}.{options.format}
--baseUrl [baseUrl] base url of openai api (default: "https://api.openai.com")
--verbose verbose output (default: false)
--userPublicId [userPublicId] user public id
-V, --version output the version number
-h, --help display help for command
Note that if you are in China or other regions where access to the openai API is not possible, you can use the --baseUrl parameter to specify a mirror address, such as https://openai.ai-assist.moe, which can be deployed to a Cloudflare Worker at zero cost through the open source project openai-proxy.
My node.js fetch code can’t work either. But if I copy curl from chrome, it works.
Is this tool still working or openai has raised protection for API endpoints?
Release 0.1.9 fixed, it seems that openai modified the http header part, I made some adjustments, it works now. Another reminder, if you are in an area where you cannot access the openai api, please configure the proxy correctly, or use a mirror service, and refer to the updated baseUrl field.
In the end, I created a chrome extension to export it, so I didn’t need to install any runtime locally, and I didn’t need the command line. The chrome store is currently under review, and the zip of the plugin has been built and can be installed locally to try.
OpenAI has locked down the usage API that the platform site uses pretty hard against bots. What was an “undocumented API” is now a “good luck” API.
However, you can look at the administration API surface, needing generation of an admin key. See if the resources you want are right there.