Short answer: For a text summarization API cost comparison in Node.js, choose the model that clears your quality and latency gates at the lowest measured accepted cost, then recheck the result against the real gaming report mix.

A gaming moderation queue needs a short, faithful summary quickly; a cheap model that drops the target, threat, or evidence creates review work and can increase latency through retries. The comparison is about the whole workflow, not a headline token price.

I would route reports through a small evaluation harness, keep the model behind a provider-neutral interface, and record input tokens, output tokens, elapsed time, retry count, and reviewer outcome for every sample. The result is a decision rule you can defend.

Which model makes text summarization API cost predictable?

Price per million tokens is only one input. Moderation reports vary wildly: a one-line slur report and a long dispute with chat excerpts do not have the same prompt size. Output length matters too.…