Article
API vs Bulk Email Verification Pricing: Which Costs Less?
By Unlimited Verifier Team ·

Summary
On Unlimited Verifier, bulk upload has no per-email fee for standard verification on any plan, while API access requires the $29 monthly Pro plan. At full monthly use, the API works out to about $0.29 per 1,000 emails, but the better comparison is total cost per usable contact, including workflow time and re-check frequency.On Unlimited Verifier, bulk upload carries no per-email fee for standard verification on any plan, while API access requires Pro at $29 a month ($25 billed annually) for 100,000 emails. For planning, the API works out to $0.29 per 1,000 emails at full monthly use, so that is the number to budget against. The real gap between the two routes comes from volume and workflow, not the rate card.
Most cost confusion starts when teams compare email verification pricing models side by side without converting them to the same unit. The better question is what each route costs to clean one list, re-check it next quarter, and keep new signups clean. For the wider picture, see our email verification cost guide.
Quick answer
- Bulk upload: Standard verification has no per-email fee on any plan. Free covers 25 lists a month of up to 150 emails each (3,750 addresses at most). Pro covers lists of up to 25,000 emails each.
- API: Pro only, with 100,000 emails a month and batches of up to 10,000 emails per request. Free has no API access.
- Lowest-cost route for a one-off list: Bulk upload. For checks that must run at signup or checkout, the API is the right tool if your volume fits the monthly allowance.
- Compare on cost per usable contact, which includes staff hours, export-and-import time and deep-verification limits, not only the subscription fee.
What is the real difference between API and bulk email verification pricing?
Bulk and API verification are priced differently because vendors bill them differently. Unlimited Verifier describes one set of checks (syntax, domain, MX records and the SMTP mailbox), so the comparison is mostly about billing and workflow. Vendors typically use one of four billing models:
| Pricing model | How you pay | Where it hurts list cleaning | Best fit |
|---|---|---|---|
| Per-credit prepaid | Buy a block of credits; each check uses one | Re-checks spend credits again; unused packs may expire, depending on the vendor's terms | Occasional small checks |
| Pay-as-you-go per email | A fixed rate per check, often the same for API and upload | Cost scales linearly, so a 500,000-row clean costs the same each time you repeat it | Irregular, low-volume use |
| Subscription with included allowance | Monthly fee plus an allowance; overage terms vary | Unused allowance is paid for and lost | Steady, predictable volume |
| Unlimited standard, capped deep (Unlimited Verifier's structure) | Flat monthly fee; standard verification unlimited on bulk, within list limits; deep verifications capped monthly | The deep cap sets the pace if you want deep checks on a whole large list | Recurring list hygiene and mixed API use |
Under per-credit billing, every re-check of the same list is a new charge. Under unlimited standard verification, re-running a list after cleanup adds no per-email cost, though plan limits such as list count still apply.
Bottom line: Compare billing models before rates. A low price per check can still cost more than a flat fee once you re-check a list.
How does Unlimited Verifier price bulk uploads versus API calls?
Bulk and API access sit on different plans, and that changes the comparison. This table uses Unlimited Verifier's published plan facts:
| Feature | Free ($0) | Pro ($29/month, or $25/month billed annually) |
|---|---|---|
| Standard verification | Unlimited, no per-email fee | Unlimited, no per-email fee |
| Lists per month | 25 | Unlimited |
| Emails per list | Up to 150 | Up to 25,000 |
| Maximum bulk addresses per month | 3,750 (25 × 150) | No list-count cap listed |
| Deep verifications per month | 750 | 25,000 |
| API access | None | 100,000 emails a month |
| Results retained | 24 hours | 30 days |
| File format and size | CSV or Excel, up to 10MB | CSV or Excel, up to 10MB |
Two details matter more than the headline price:
- Results retention. On Free, results disappear after 24 hours. On Pro, they stay for 30 days. If you don't export, you pay in staff time to re-run the list.
- File size. A bare email column runs about 27 bytes per row, so 25,000 addresses come to roughly 0.7MB. That estimate will vary with your data, but the 10MB limit rarely binds for lean files. Wide exports with dozens of columns can hit it, so strip unneeded fields first.
Bottom line: Bulk upload covers list cleaning on every plan. API access starts at Pro, so budget for it there.
What does the API allowance really cost per 1,000 emails?
At full use, Pro's API allowance costs $0.29 per 1,000 emails on monthly billing and $0.25 per 1,000 on annual billing. The effective rate rises fast when you use less of the allowance, and that is the number most teams miss.
The table assumes the whole subscription is attributed to API use:
| Monthly API emails used | Effective cost per 1,000 (monthly, $29) | Effective cost per 1,000 (annual, $25) |
|---|---|---|
| 10,000 | $2.90 | $2.50 |
| 50,000 | $0.58 | $0.50 |
| 100,000 | $0.29 | $0.25 |
Two notes. First, this is an effective cost, not a rate card. Second, the subscription also covers unlimited bulk standard verification, so teams using both routes pay less per API check than these figures suggest. For planning, use $0.29 per 1,000 as your ceiling.
Annual billing saves $4 a month, or $48 a year. That's worth it only if you expect the account to stay active for twelve months. For the trade-offs, see annual vs monthly billing for email verification.
Bottom line: If you use most of the 100,000-email allowance, Pro's API cost stays below $0.30 per 1,000. If you use a small share, the per-1,000 cost climbs steeply.
How much does a 500,000-email list cost each way?
A 500,000-email one-off clean costs $29 on Pro through bulk upload. The same list through the API would take five months of the monthly allowance, which makes bulk the better route for a single large job. For the broader pricing question, see how much it costs to verify 500,000 emails.
Bulk route
- Split the list into 25,000-email files: 500,000 ÷ 25,000 = 20 files.
- Check file size: 25,000 rows × ~27 bytes ≈ 0.7MB per file, well inside the 10MB limit.
- Run standard verification on all 500,000 addresses. It's unlimited on Pro, so the cost is the subscription: $29 for the month.
- Spend deep verifications on the riskiest subset. Pro includes 25,000 a month, so the first 25,000 riskiest addresses fit in one month's allowance.
API route
- Batch the list into 10,000-email requests: 500,000 ÷ 10,000 = 50 requests.
- Note the constraint: 500,000 is five times the 100,000-email monthly allowance. Finishing takes five months of Pro, so the total is 5 × $29 = $145, and the list isn't clean until month five.
| Route | Plan | Time to finish | Subscription cost |
|---|---|---|---|
| Bulk upload | Pro | One month | $29 |
| API | Pro | Five months of allowance | $145 |
| Hypothetical per-credit vendor at $1.00 per 1,000 | Illustrative | One pass | $500 per pass, plus $500 for each re-check |
The per-credit row is illustrative, not a quoted price. Its point is structural: per-credit billing charges you for every pass.
Bottom line: For a one-off 500,000-row clean, bulk upload finishes in one month for $29. The API needs five months to cover the same list.
Which path is cheaper for always-on verification?
For always-on checks, the API is cheapest at the margin when volume fits the monthly allowance. The total cost, though, depends on engineering time as much as the subscription. This is where email verification for ecommerce and SaaS teams usually need to make a real decision.
Take a company with 8,000 new signups a month and a 200,000-contact database re-checked each quarter:
- Signups via API: 8,000 checks use 8% of the 100,000-email allowance. The marginal cost is $0 on top of Pro.
- Quarterly database re-check via bulk: 200,000 addresses uploaded as eight 25,000-email files. Standard verification is unlimited, so the cost stays at $29 a month.
The hidden cost is engineering. Building batching, retries, rate handling and logging might take a developer 12 hours. At a hypothetical loaded rate of $75 an hour, that's $900, or about 31 months of Pro. For a small team, scheduled bulk uploads often beat the API on total cost until latency or volume forces the issue.
The API earns its place when a check must run before the record is saved, such as a signup form that rejects a bad address. That's the case for real-time email validation. Whether real-time checks cost more overall is covered in is real-time verification more expensive than bulk.
Bottom line: Use the API when the check has to happen before the record is saved. Use scheduled bulk uploads when the check can wait.
What hidden costs change the real price?
Five hidden costs can move the real price more than the subscription fee:
- Deep-verification caps. Free includes 750 a month and Pro 25,000. If every address on a 200,000-row list needed a deep check, Pro's cap would take about eight months to clear. Rank addresses by risk and spend deep checks where the answer changes a decision.
- Results expiry. Free keeps results for 24 hours, Pro for 30 days. Export Valid, Risky and Invalid files the same day you run a list.
- Manual handoffs. Unlimited Verifier has no native ESP, CRM or Zapier integrations. A bulk workflow means exporting a CSV, verifying it and re-importing the Valid contacts. Budget staff time for that, or script it against the API.
- Unknown results. Some vendors bill for addresses they can't confirm, and retries can double a charge. Read do email verifiers charge for unknown results before comparing rates.
- Unused allowances. An included allowance is only worth something if you use it. Match your monthly plan to real volume, and see what happens to unused email verification credits for how other models treat leftovers.
For the broader cost picture, see how much email verification costs in 2026.
Bottom line: Price the workflow, not just the plan. Export time, deep-check scheduling and unknown-result billing often matter more than the monthly fee.
How do you choose between API and bulk verification?
Answer four questions in order: how often you verify, whether the check must block a record, who maintains the integration, and what each route costs per usable contact.
- Count your monthly volume. Separate one-off cleans, recurring list checks and live checks. A 500,000-row clean and 8,000 signups a month call for different routes.
- Decide whether the check must block. If a bad address must be rejected before it's saved, use the API. If you can clean the list later, use bulk.
- Check engineering capacity. If nobody can maintain batching, retries and error handling, bulk uploads are the realistic option.
- Calculate cost per usable contact. Divide total spend (subscription, staff hours and any re-runs) by the Valid contacts you keep. Does verifying emails lower your ESP bill shows how the same logic applies to sending costs.
| Scenario | Best route | Why |
|---|---|---|
| Cleaning a 60,000-row list before a reactivation campaign | Bulk upload | One-off, large, no integration needed |
| Rejecting bad addresses at signup | API | Must run before the record is saved |
| Monthly re-check of a 150,000-contact CRM export | Bulk upload on Pro | Scheduled batch; standard verification unlimited |
| Checking a few addresses by hand | Free email checker | No API or bulk setup needed |
| Engineering team building a data pipeline | API, within the 100,000-email allowance | Batch and request model fits automation |
Before committing, test both routes on a sample. The how to choose an email verifier guide covers evaluation criteria, and our roundup of best email verification tools places pricing alongside accuracy and integration options.
Bottom line: Let the blocking requirement and team capacity decide the route. Let cost per usable contact decide between two routes that both work.
How do you price your own list in 30 minutes?
You can estimate your real cost from a row count and a few plan limits, then confirm it with one sample upload.
- Count your rows. Open the export in a spreadsheet or count lines in a terminal. Subtract the header row.
- Work out the list count. Divide the total by 25,000 and round up. A 73,000-row list needs three lists on Pro (73,000 ÷ 25,000 = 2.92, rounded up to 3).
- Check file size. Export only the email column plus any fields you need for segmentation. Anything over 10MB needs splitting.
- Pick your plan. Under 3,750 addresses a month fits Free's bulk allowance. Anything larger, or any API use, needs Pro.
- Set your deep-check budget. Multiply the addresses you want checked deeply by your monthly allowance (750 on Free, 25,000 on Pro) to see how many months a full pass would take. Rank by risk: catch-all domains, role accounts and imported leads come first.
- Run a sample upload. Start with the Upload and verify a list tool. Use the Free email checker to spot-check odd addresses, and review the Catch-all email verification page to understand how catch-all results are handled.
- Test the API on Pro. Create a key on the Email verification API page, send one 10,000-email batch, and track usage against the 100,000-email allowance.
- Save your counts. Record the Valid, Risky and Invalid totals and the time spent in one sheet, so next month's estimate uses real data. Build that habit into your email list maintenance best practices schedule.
If you don't have an account yet, sign up on the Free plan to test the upload flow before you choose Pro.
Bottom line: A row count, a plan limit and one sample run give you a defensible cost estimate in under an hour.
What are the common mistakes that inflate verification costs?
Most overspending comes from a few predictable errors:
- Comparing per-email rates across billing models. A per-credit rate and a subscription don't compare directly. Convert both to cost for your real volume and frequency.
- Paying for the same list twice. Under per-credit billing, every re-check is a new charge. Re-run only addresses that changed or were never checked.
- Buying API capacity you won't use. At $29 a month, an unused 100,000-email allowance is a fixed cost with no return. Start with bulk and add the API when a live check becomes necessary.
- Ignoring the 24-hour retention window on Free. Export the same day, or your second run costs staff time.
- Skipping verification to save money. Bounces from unverified addresses can cost more than the verification you skipped. The cost of not verifying your email list quantifies that trade-off.
- Spending deep checks on addresses that already look clean. Deep verifications are capped. Spend them on Risky and catch-all addresses, where the result changes the decision.
- Treating verification as consent. A deliverable address isn't an opted-in one. Keep email verification compliance and hygiene as a separate control.
Bottom line: Most inflated costs come from double-paying for re-checks, buying allowances you won't use and losing results before you export them.
How we compared (and limitations)
This article draws on Unlimited Verifier's published plan facts and on public documentation for the standards it references. We haven't tested competitors' pricing, and we describe other vendors' billing models by structure, not by current rates. Prices change often and vary by contract.
Limitations to keep in mind:
- The 99.5% accuracy figure for deep verification is Unlimited Verifier's own stated number, not an independent benchmark.
- The worked examples use Unlimited Verifier's real limits. The $1.00 per 1,000 per-credit price and the $75 hourly developer rate are hypothetical and exist only to show the arithmetic.
- The 27-bytes-per-row file size is an estimate for a bare email column. Check your own export.
- We haven't confirmed in every case how deep and standard checks apply to API calls. Confirm allowance rules on the current plan page before budgeting a large API project.
- Mailbox providers' sender rules shape how much clean data is worth. Google's sender guidelines set expectations for bulk senders, and those rules change, so check them directly.
- SMTP mailbox checks rely on the protocol described in RFC 5321, and bounce meanings follow the enhanced status codes in RFC 3463. Some servers respond inconsistently, so no single check is perfect.
To see how the checks work before you rely on them, the verification engine is open source on GitHub.
Cost per 1,000 emails at full Pro use
| Route | Plan | Monthly price | Allowance | Approx. cost per 1,000 |
|---|---|---|---|---|
| API | Pro (monthly) | $29 | 100,000 emails | $0.29 |
| API | Pro (annual billing) | $25/mo billed annually | 100,000 emails | $0.25 |
| Bulk upload | Free | $0 | 3,750 emails max | No per-email fee |
| Bulk upload | Pro | $29 | Lists up to 25,000 emails each | No per-email fee |
Frequently asked questions
Is bulk email verification free on Unlimited Verifier?
Standard bulk verification carries no per-email fee on any Unlimited Verifier plan, including Free. Free covers 25 lists a month of up to 150 emails each, so the most you can check on Free is 3,750 addresses per month. Pro allows lists of up to 25,000 emails each. Plan limits such as list count still apply.
Does the Free plan include API access?
No. According to the article's plan facts, API access is available only on Pro. Teams that need checks at signup or checkout must upgrade to Pro, while one-off list cleaning can run on the bulk upload route at no per-email cost.
How much does API email verification cost per 1,000 emails?
At full monthly use of Pro's 100,000-email allowance, the API works out to about $0.29 per 1,000 emails, based on the $29 monthly price. On the annual billing option of $25 per month, the effective rate is lower. Use this figure for budgeting, but check whether you will actually use the full allowance.
When should I use the API instead of bulk upload?
Use the API when verification must happen in real time, such as at signup or checkout, where a list upload is too slow. Bulk upload suits periodic list cleaning. If your volume fits the monthly API allowance, the API covers real-time needs without extra per-email charges.
What is the maximum batch size for API requests?
Pro API access supports batches of up to 10,000 emails per request, according to the article. Larger jobs need to be split into multiple requests. Batch size affects how quickly you can process a large list through the API versus uploading the file directly.
Why is cost per email a misleading comparison?
A low price per check can cost more than a flat fee when you repeatedly re-check the same list. Under per-credit or pay-as-you-go billing, each re-check adds a charge, while unlimited standard verification adds no per-email cost on re-runs. Compare total cost per usable contact, including staff hours and export-import time.
Does deep verification have a separate cost?
Deep verifications are capped monthly on Unlimited Verifier's structure, so the cap, not the per-email rate, sets the pace if you want deep checks across a whole large list. Standard verification remains unlimited on bulk uploads within list limits. Check the current plan page for the exact deep verification allowance.
Which route is cheaper for a one-off list cleanup?
Bulk upload is usually the lowest-cost route for a one-off list because standard verification has no per-email fee on any plan. You only need a plan that fits the list size, such as Free for lists up to 150 emails each or Pro for lists up to 25,000 emails each.
How do I compare verification vendors fairly?
Convert every vendor's pricing to the same unit, such as cost per 1,000 emails, and include how often you will re-check the list. Then factor in workflow costs like manual exports, imports, and deep-verification limits. A vendor with a low rate card can still cost more in total than a flat-fee plan.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.