Bulk email verifier — insufficient credits, restarts, and JSON errors

If you've hit "insufficient credits" while having credits, "Unexpected token 'R', 'Request En'... is not valid JSON", a job that restarts at 30%, or "bulk verification not working" — read on.

Verification credits ≠ lead credits

Consulti has two separate credit pools:

| Credit type | Used for | |---|---| | lead_credits | Unlocking leads from the B2B / Local / Creator databases | | verification_credits | External email verification (Bulk Verifier, Single Verify, Email Finder) |

If you see "insufficient credits" in the Bulk Verifier and your dashboard shows 1,000 credits, those are almost always lead_credits, not verification_credits.

| Plan | Monthly verification_credits | |---|---| | Free | 500 | | Pro | 5,000 | | Scale | 25,000 | | Enterprise | 100,000 |

To check your verification_credits balance specifically, go to Settings → Subscription — both pools are shown separately.

"Verifying emails from leads I unlocked" is free

If the email came from a lead inside a Consulti database (B2B, Local, Creator), you do not need verification credits to verify it — those leads are already verified. Verification credits are only consumed for external emails (your own list uploaded as CSV, manually-entered emails, scraped-elsewhere lists).

"Unexpected token 'R', 'Request En'..." JSON error

This error means the server returned a non-JSON response that the browser tried to parse as JSON. The most common cause: your CSV upload exceeded the 50MB file size limit and the server returned a "Request Entity Too Large" HTML error page instead of a JSON response.

Fix: Split your CSV into smaller files (under 50MB each — usually means under ~250,000 rows depending on column count). You can submit multiple jobs sequentially.

Other causes of the same error:

• Vercel function timeout (60 seconds) on a very large file — same fix, smaller batches.
• Network interruption mid-upload — retry on a stable connection.

Job restarts at 30% / lost progress

If a bulk verification job stalls and restarts:

1. The restart is automatic — partial results from the first run are saved.
2. Go to Bulk Verifier → Job History (or /tools/bulk-verifier).
3. Find the failed job and click Download partial results — it returns the rows that completed before the restart.
4. Remove those completed rows from your source CSV and re-submit the remainder.

The system also caps you at 10 verification jobs per hour to prevent runaway loops. If you hit "Rate limit exceeded. Maximum 10 verification jobs per hour", wait an hour or contact support to lift the cap for a one-time large project.

Bulk verifier rate of progress

A typical bulk job verifies roughly 22–40 emails per minute depending on the mix of providers in your list. A 5,000-row file should take 2–4 hours end-to-end. If your job has been "running" for more than 6 hours with no progress, it's likely stuck — check the job page for an error and re-submit if needed.

Still stuck?

Submit a ticket with:

• The exact error message (screenshot if possible)
• File size and row count of your upload
• The job ID from the URL (e.g., /tools/bulk-verifier/jobs/abc123)

"Bulk verification doesn't work" is hard to debug; the above turns it into a single fix.