Is the Anthropic batch queue predictable?

We measure it: claude-haiku-4-5 runs a spread of 2.4x (p90 5 min over p50 2 min), so the tail sits a known distance from the median. A tight spread means the median is safe to book a deadline against - which is a real part of whether the batch API is worth it, not just the 50% price cut.

Is the Anthropic batch API worth the wait?

For most workloads, yes. It is 50% cheaper, and half of claude-haiku-4-5 jobs finished within 2 min in our measurements - well inside the 24 hours window Anthropic promises. The only question is your deadline, which is why batchwatch answers against a max_wait you supply rather than guessing one.

How much does the Anthropic batch API save?

50% of the synchronous price, on both input and output tokens. That is Anthropic's own published batch rate, not a batchwatch estimate.

Is the Anthropic Message Batches API worth it?

The answer

Anthropic's batch endpoint costs 50% of the synchronous rate - their own published price, on every input and output token. That is a real, immediate saving on any workload that does not need an answer this second.

And the wait is shorter than the "within 24 hours" ceiling suggests: we measured a median of 2 min for claude-haiku-4-5, with nine in ten jobs finishing within 5 min. For most pipelines that is an easy trade - half the cost for a wait you can plan around.

There is a second half to "worth it" that price alone misses: how predictable the queue is. claude-haiku-4-5's spread - its p90 over its p50 - is 2.4x: the tighter that number, the more a median is safe to plan on. batchwatch measures it per model, so you can pick on consistency, not just on the headline wait.

The full numbers, per model

Questions this answers

Is the Anthropic batch queue predictable?: We measure it: claude-haiku-4-5 runs a spread of 2.4x (p90 5 min over p50 2 min), so the tail sits a known distance from the median. A tight spread means the median is safe to book a deadline against - which is a real part of whether the batch API is worth it, not just the 50% price cut.
Is the Anthropic batch API worth the wait?: For most workloads, yes. It is 50% cheaper, and half of claude-haiku-4-5 jobs finished within 2 min in our measurements - well inside the 24 hours window Anthropic promises. The only question is your deadline, which is why batchwatch answers against a max_wait you supply rather than guessing one.
How much does the Anthropic batch API save?: 50% of the synchronous price, on both input and output tokens. That is Anthropic's own published batch rate, not a batchwatch estimate.

See it live

Every number here is measured, and it is all public.

The live dashboard shows every model with its distribution, n and confidence grade. /v1/coverage is the same data as JSON, no key required. Send five measurements in seven days and the delay is gone: you read every figure live, and the decision endpoints open (/v1/should-i-batch, /v1/estimate-batchtime).