Batch search (row-in / row-out bulk lookups)

Runs many queries in one call — offenders.io CSV-batch parity (one row = one call in, one result out). Each row goes through the SAME engine as /v1/search (served from the current snapshot), with bounded server-side concurrency, and results come back in input order. Send either a JSON array of query objects, a JSON envelope { "queries": [...], ...batch-wide options } (the non-queries keys — jurisdictions, freshness, match, recordTypes, locationScoped, include — apply to every row), or a text/csv body whose header row names Query fields (firstName,lastName,state,dob,city,zipcode,address,age,q). A row that fails is reported with status: error in place; it never aborts the batch. Max 1000 rows. Accepts an API key OR a session token.

Billing — per search, NOT per request. A batch is one HTTP call but contains N searches, and each search in the batch is billed as one search (at the graduated per-call rate). A batch of 100 rows = 100 billable searches. Batch is cache-only (Regular): the retired freshness tier no longer applies, and live re-verification is not offered per row.