Glossary · Building
noun
Sending many API requests to be processed together, rather than one at a time, in exchange for lower cost and slower turnaround. Suited to non-urgent, high-volume work.
In practice
Batch processing suits work that does not need an instant answer: classifying a backlog of support tickets overnight, summarising a large archive of documents or tagging thousands of product descriptions. Requests are sent together and returned later, at a lower cost than sending them one at a time. It is a back-office technique that usually sits inside a custom tool built on the API.
When you have a large volume of similar tasks and can wait for results, for example processing a month of records or a document archive. For anything a person is waiting on, standard requests are the better fit.
From AI curious to AI capable
Start with an audit. You will know exactly where AI fits, what to do first and what it should give back. Your report looks something like this.
Prepared for
your business
What Claude can really do
Contents
Every opportunity mapped, scored and turned into a costed Claude roadmap.