FDE-AI Latency, Token Economics & Batch Systems EASY
PRODUCTION SCENARIO
A telecom classifies 40,000 closed support tickets every night into root-cause categories for a dashboard analysts open the next morning. The job runs through the real-time Messages API with 20 parallel workers and costs about $600 a night.

Which change cuts the cost most while still meeting the morning deadline?

Answering here is anonymous. Nothing is saved unless you sign in.

Show answer and explanation

Answer: Submit the whole night's tickets as a single Message Batch job

The Message Batches API charges 50 percent of standard prices for asynchronous work, and most batches complete within an hour, with results available once every request has finished or after 24 hours, whichever comes first, which clears a next-morning dashboard. Ticket text never repeats, so a cache is never read back. Tokens are billed per token, not per hour, so 100 workers change wall-clock time and rate-limit pressure rather than the bill. Streaming changes when tokens arrive, not what they cost.
Free

Keep practicing FDE-AI

24 original FDE-AI practice questions, each with an explanation and a source link. No account needed.

Start free practice set → Timed, explained, free