the Verifier checks lists you already own. It has clear ceilings, all of which have a workaround.
Rows per run
Up to 1,000 emails per run - split larger lists.
The in-app verifier handles 1,000 addresses per run. For bigger lists use the CLI, which splits automatically:
npx argorant verify --file my-list.csvAPI batch sizes
Up to 500 emails per batch - split larger lists (the CLI does this automatically).
Too many records in one request (max 10,000)
The batch verify endpoint takes 500 addresses per call. Loop over batches rather than sending one enormous request, and back off on a 429 instead of retrying immediately.
Files that are rejected
Only CSV and Excel files are supported
File too large (max 15MB)
Empty file
CSV has no headers
Could not parse CSV text
Export from your spreadsheet as CSV with a header row, one address per row, UTF-8. A file exported straight out of a CRM often carries a preamble above the header, which is the usual cause of a parse failure. Delete everything above the header row.
No addresses found
No valid email addresses found in your list.
No valid email addresses provided.
API rows must include at least one valid email
The file parsed but no column contained something shaped like an address. Check that the email column is not stored as a formula, and that addresses were not truncated by a column width setting during a copy-paste.
Nothing is billed for a rejected file, and within a run you are billed only for fresh checks. Addresses checked recently are answered from that result for free.