Speculative fan-out
Speculative fan-out: send many questions in one request, including questions that only matter for some inputs. If the ticket is not a bug, ignore severity. You already paid a few question tokens and almost no extra latency.
TypeSafe publishes a Parallel questions cookbook that runs a multi-question briefing over a long Wikipedia article and reports that batching beats one-question-per-call on both cost and latency, with no change in answers. Their docs index and primitives page quote slightly different multiples for that cookbook; we will not pick a number. Read the cookbook for the current figure.
Why answers stay stable
Questions are independent. Extra questions are not supposed to rot the others’ context. (Unrelated state still can; that is a different warning.)
Agent habit to break
One question per HTTP call wastes the request budget and re-sends state. Install the agent skill so tools batch.
When a second request is truly required — you need the first answer to fetch documents or to build the next option list — that is sequential workflow, not fan-out. TypeSafe calls out skill suggestion, structure recovery, and hierarchical classification as examples that earn a second round trip.
Sources
Public TypeSafe or adjacent documentation only. No private claims.