Email Verifier Pricing and Credit Packs

Every TrekMail plan includes monthly Email Verifier credits. Buy a pack only when the included allowance does not cover the job you need to run. The table below lists the USD base prices; checkout shows the applicable account currency.

Included monthly credits

Monthly credits do not roll over. Purchased credits remain available until used.

Credit packs

The per-verification figure assumes Quick mode. The price is lower per address in larger packs because each credit has the same verification value.

Quick and Deep costs

The Deep estimate is based on the actual domains in your list. Do not budget from a flat "two credits for every address" rule if your list includes large mailbox providers. The estimate before submission and the credits_charged field in the API response are authoritative for that job.

Reference credit requirements

The Deep column is an upper bound, not an invoice. It is useful for deciding whether the current balance is in the right range. Prepare the list to see the actual total before checkout or submission.

What affects the final Deep total

The Deep estimate separates the addresses for which the extra mailbox-level work can be requested from addresses at providers where that work is intentionally skipped. That is why two lists of the same size can have different Deep totals. The difference comes from provider mix, not from a hidden plan tier or a change in the price of a purchased credit.

The actual submission response reports credits_charged, plus probe, skip and deep_savings counts for integrations. Keep these values with an automated job record rather than trying to reconstruct the cost from a later export.

Plan a job

Use this simple calculation for a Quick job:

unique addresses × 1 credit

For Deep, start with two credits per address, then use the dashboard estimate to account for addresses billed at the 1-credit rate. A 10,000-address Quick job needs 10,000 credits. A 10,000-address Deep job can need up to 20,000 credits, but may cost less depending on its provider mix.

Remember to subtract the monthly allowance currently available before buying a pack. On the regular TrekMail host that allowance is used first. On White Label hosts, verification uses purchased credits only.

Example planning paths

A small clean-up. You have 300 contacts and 100 monthly credits. A Quick job needs 300 credits, so the remaining gap is 200. A purchased balance larger than that stays available for the next job.

A large new import. You have a 20,000-contact export and do not know its quality. Run a small Quick sample first. If the sample and collection history justify a deeper review, prepare the full list in Deep mode and use its exact estimate. That is safer than buying a large pack based only on a flat calculation.

Ongoing maintenance. If your monthly usage is predictable, let the included allowance cover routine Quick checks and buy only when a campaign or import exceeds it. Purchased credits do not expire, so a sensible buffer can support a later recheck without forcing a recurring subscription decision.

Match the purchase to the decision

Choose a pack without overcomplicating it

1. Prepare the list in the verifier and check the estimated credit total.
2. Compare that total with the available balance shown in the dashboard.
3. Choose the smallest pack that covers the gap, unless you know you will use the remaining credits later.
4. Keep a small buffer if you plan to rerun a sample or a corrected segment.

The smallest pack is not always the best choice. Compare the cost of the smallest pack that covers the gap with the next tier only when you have a realistic upcoming use. Buying a much larger pack solely to chase the lowest unit rate is not useful if the contacts will never be verified.

Before and after checkout

Before buying, confirm the host and account that will run the verification. Credits are tied to that account. After checkout, return to the verifier and confirm the balance before starting the job. Do not paste payment details into a support request. If a purchase needs investigation, provide the job name or purchase reference shown in the dashboard rather than payment credentials.

Keep pricing separate from sending eligibility

Credits pay for a technical review. They do not add mail-sending capacity, change your plan's sending limits, make a domain active or allow a campaign that does not meet permission requirements. Plan the verification cost first, then apply the result within your normal sending and consent rules.

A practical purchase checklist

1. Confirm the account and host that will submit the job.
2. Prepare the list and inspect its unique-address count.
3. Choose Quick or Deep for a documented reason.
4. Read the exact estimate and compare it with the current available balance.
5. Buy the smallest reasonable pack for the gap.
6. Start the job, save its ID and download the finished result within 15 days.

This process makes the price visible before the work begins and preserves enough context to understand a later charge without relying on a fixed time estimate or a generic mode description.

Results remain available for 15 days. Download the export you need, then use campaign bounces and opt-outs to improve the source list rather than treating a purchase as a substitute for list quality.

For balance, reset and cancellation details, read How Email Verifier Credits Work.