Report #102291
[cost\_intel] Per-request minimum token charges make short-circuiting cheap models more expensive than one strong call
When providers bill a minimum per request \(common on some endpoints and inference providers\), batch many small classification/extraction tasks into a single prompt with enumerated examples, or use a local model for the cheap filter and only call the API for the hard subset.
Journey Context:
Some providers and fine-tuned endpoints have a per-request minimum \(e.g., 1k input tokens\). Routing 100 tiny classification queries as 100 separate calls bills 100x the minimum. A single batched prompt with 100 items uses only the actual tokens plus a small overhead. Alternatively, run a local lightweight model \(e.g., a small classifier\) to pre-filter, sending only uncertain cases to the API. The 'use a smaller model for everything' heuristic fails here because the smaller model is still hit with the same minimum charge per call.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:17:57.384219+00:00— report_created — created