REST: POST /api/mcp/email/verify and /verify/batch

The verify endpoints check addresses you already have. This is separate from contact credits: it draws on your verification-check pool, and recent re-checks are free.

Single address

curl -X POST -H "Authorization: Bearer ag_live_..." \
  -H "Content-Type: application/json" \
  -d '{"email": "someone@company.com"}' \
  https://argorant.com/api/mcp/email/verify

The response carries the address, a status and a deliverable flag. The deliverable flag is what your code should branch on.

Batch

curl -X POST -H "Authorization: Bearer ag_live_..." \
  -H "Content-Type: application/json" \
  -d '{"emails": ["a@company.com", "b@company.com"]}' \
  https://argorant.com/api/mcp/email/verify/batch

Send up to 500 addresses per request and chunk anything larger. The batch response returns a result row per address plus two counters: how many checks were billed, and how many were served from a recent check and therefore free.

Batch verify response with results plus billed and cached counters

Notes

Deduplicate before sending. Duplicate addresses in one payload waste checks.
Catch-all mailboxes accept everything, so no verifier can fully resolve them. They are labelled honestly rather than guessed at.
Contacts exported from Argorant are already verified at export time. Use these endpoints for lists that came from somewhere else.

The CLI equivalent is argorant verify, including a CSV mode that chunks the file for you.