How to Export and Read Your OpenAI Usage CSV (and Find the Hidden Costs)

OpenAI's usage export is a goldmine most developers never open. From the OpenAI platform dashboard, go to Usage, pick a date range that covers a full billing cycle, and export the CSV. Each row is roughly a model, a day, and its token counts, sometimes split further by project or API key. That flat file is enough to reconstruct your entire spend and spot the leaks.

Where the hidden costs hide

The hidden costs hide in three places. First, the input and output columns are billed at very different rates, output usually costs several times more per token, so a workload that generates long responses is priced completely differently from one that reads long documents. Second, models you forgot were running: an old fine-tune, a stray evaluation job, or a debugging script left on a cron schedule can quietly account for a surprising share of the total. Third, embeddings and smaller models look free per call but add up at volume. Reading the CSV row by row is where these show up.

Skip the spreadsheet

Rather than build a spreadsheet, paste the exported CSV straight into the bill auditor. It maps OpenAI's column names automatically, sums your tokens per model, and prices the same usage on cheaper alternatives, so within seconds you go from a raw export to a ranked list of where the money went and what it would cost elsewhere. The parsing happens locally, so the file never leaves your machine.