Runs up to 100 ads.txt verifications in a single call — the endpoint an
ad-buying agent uses for pre-bid checks across a whole campaign's supply.
Each item is the same shape as `sigil_verify_ads_txt`. Per-item
validation failures are reported inline; the batch never fails as a
whole. Publisher records are fetched once per unique domain.
Use this tool when:
- You are evaluating many supply paths at once (campaign setup, SPO sweep).
- You want one round-trip instead of N calls to `sigil_verify_ads_txt`.
Inputs:
- `items` (body, required): Array of 1–100 verification requests, each
`{ publisher_domain, exchange_domain, seller_id, seller_type? }`.
- `resolve_chain` (body, optional): Applies to every item — when true, a
matched RESELLER entry is cross-checked against the exchange's sellers.json.
Returns:
- `count`: number of result entries (matches `items` length, in order).
- `verified_count`: how many resolved to `verified: true`.
- `results`: array aligned to `items`. Each entry is either a verification
result with `ok: true` and `input_index`, or `{ ok: false, input_index,
error, message }` for an invalid item.
Cost:
- Counts as one request against the daily rate limit.
Latency:
- Typical: <150ms. With `resolve_chain: true`, add one sellers.json fetch
per unique exchange (edge-cached 12h after the first fetch).
Connector