requests is a group: one content plus a list of questions about it — so asking several questions about the same content sends that content only once, and a single call can still mix groups with different content.
/decide/batch requires the same API key header as /decide. See Authentication.Request
Each question can carry its own optionalgrounding (grounding is no longer part of the group; sort questions still reject it).
Response
Batch responses are nested by group, then by question:results: one item per group (matchesrequests1:1)results[i].answers: one item per question in that group’squestions, in orderresults[i].answers[j].ok: success flag for that question (.resultholds the decision, or.errorthe message)meta.request_count: number of groupsmeta.question_count: total questions across all groups (the billing unit — see Pricing)