sigil_verify_ads_txt_batch
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 (matchesitemslength, in order).verified_count: how many resolved toverified: true.results: array aligned toitems. Each entry is either a verification result withok: trueandinput_index, or{ ok: false, input_index, error, message }for an invalid item.
Cost:
Each item costs one rate-limit unit (the first is the request itself). A batch larger than the remaining budget is refused whole with 429 and charges nothing beyond that first unit, so the effective maximum per call is min(100, remaining + 1): anonymous 10/min, free 50/day, supporter 500/day, pro 5,000/day, enterprise unlimited.
Latency:
Typical: <150ms. With
resolve_chain: true, add one sellers.json fetch per unique exchange (edge-cached 12h after the first fetch).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | 1–100 verification requests | |
| resolve_chain | No | Resolve reseller chains for every RESELLER item |