Verify up to 20 claims in one call.

Runs each claim through the pipeline concurrently (bounded). Use one persisted Idempotency-Key for the whole batch. A response-wait expiry returns 202 for the operation, not free per-item verdicts. Each completed item has its own verdict and receipt. If an item fails with an uncertain outcome, it has no receipt, billed_usd is null, and the batch requires operator reconciliation; do not resubmit under another key.

post/v1/verify/batch

Request

  • Base URL: https://api.verify-api.dev
  • URL: https://api.verify-api.dev/v1/verify/batch
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Send a unique client-generated key and persist it before submission. Same account, method, route and body replay the stored response, or return 202 while unresolved. Different body or route returns 409. Unresolved keys are never automatically reclaimed; worker loss requires reconciliation. If omitted for verification, a key is generated and returned, but cannot protect retries if that first response is lost.

Request body

max_wait_msinteger

Response wait for the entire batch, not cancellation. Per-item max_wait_ms does not cancel work or determine the batch HTTP wait.

Example request

{
  "claims": [
    {
      "claim": "The iPhone 15 launched on September 22, 2023."
    }
  ]
}

Response

Durably recorded batch response in input order. Inspect outcome; an uncertain item is not a completed verdict and the final total is unknown.

billed_usdnumber nullable required

Null if any item has an uncertain billing outcome.

confirmed_billed_usdnumber required

Sum of confirmed item charges only, not an upper bound on uncertain charges.

outcome'completed' | 'requires_reconciliation' required

Example response

{
  "verdicts": [
    {
      "id": "vrf_01J8Z3W9YQKTB7ZK7C6E7N9J5R",
      "as_of_bucket": "annual:2026-Q3"
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.