Budget a bulk summarization job before you run it
Summarizing one document is cheap. Summarizing 10,000 of them is a line item. This calculator turns a document count, average length, and summary length into total token volume, then prices it for single-pass and map-reduce strategies so you can pick the cheapest approach that still fits your model’s context window.
How the two strategies are priced
Single-pass sends each whole document as input and returns one summary:
per_doc = (doc_tokens/1e6 × in_price) + (summary_tokens/1e6 × out_price)
total = per_doc × document_count
Map-reduce splits each document into chunks, summarizes every chunk (the “map”), then summarizes those chunk-summaries into a final summary (the “reduce”). It re-reads the document once as map input and adds a reduce step, so it costs more tokens but works on documents far larger than the context window.
Tips to cut the bill
For non-urgent jobs, use a provider batch tier (around 50% off). Prefer a cheap model (GPT-4o mini, Claude Haiku, Gemini Flash) for the map step and a stronger model only for the final reduce. And keep summaries short — output tokens are the most expensive part of every call.