Verify Batch

Fan-out wrapper around /verify for multi-claim LLM responses.

Body: {claims: [{text, source_url?, webhook_url?, visibility?, depth?}, ...]} capped at 20 items. Server pre-checks total credits, then fans out N independent pipelines — each with its own task_id and lifecycle. Each claim's webhook (per-item override, or batch webhook_url, or per-key default) fires when its pipeline terminates. batch_id is purely for client-side correlation; the server doesn't gate anything on it.

On a mid-fan-out enqueue error, the response includes the partial items list and a partial: true flag. Per-claim credit spend happens at each claim's normal persist time — claims that never enqueue are never charged.

depth works like visibility: a batch-wide default that any item can override. See POST /verify for what the values mean.

Each item carries its claim in claim (text is accepted as an alias), plus the same optional fields as POST /verify.

Versions. 202: 2026-10-11 receives BatchAcceptedOut, 2026-05-13 receives BatchAcceptedOutLegacy; 422: 2026-10-11 receives ValidationErrorOut, 2026-05-13 receives ValidationErrorOutLegacy; default: 2026-10-11 receives ErrorOut, 2026-05-13 receives ErrorOutLegacy.