Batch capture
also known as: search batch
Submitting many prompts, across surfaces and regions, in a single request instead of one call per query. A batch fans out into independent child captures, each billed and completed on its own, so a nightly sweep of hundreds of prompts is one request cycle rather than hundreds of round trips.
In AI Search API
POST /v1/search/batch accepts an items array of up to 500 prompts, each with its own surfaces and regions, and returns one parent job whose children resolve independently, a failure or an absence in one item never blocks or corrupts the rest. Combined with webhooks, a batch is how visibility-monitoring and share-of-voice workflows run a whole prompt basket on a schedule without hand-rolled request queues. Idempotency keys apply per item, so a retried batch submission on a cron schedule never double-bills or forks a record. Every child in a batch still returns the identical Envelope shape as a single-item request, batching changes how you submit, never what comes back.
{
"items": [
{ "query": "best crm for startups",
"surfaces": ["chatgpt", "perplexity"],
"regions": [{ "country": "US" }] },
{ "query": "top crm tools 2026",
"surfaces": ["chatgpt", "perplexity"],
"regions": [{ "country": "US" }] }
]
}Related terms
See it in the product
Every definition here is enforced in the Envelope contract. Run a capture and read the fields yourself.