How are credits charged?

Credit costs by method:

• • Fast Check — 0.5 credits per check
• • Deep Verification — 1 credit per check
• • Send to Verify — 1 credit at the integration verification step
• • API (/api/verify) — 1 credit per call
• • Dashboard / Bulk Upload — 1 credit per email

Deep Verification caching (10 seconds):

For integrations using Deep Verification, results are cached per email address for 10 seconds. If the widget check and the PHP loader check both run within that window, they share one credit — the second check reads the cached result at no charge. Your account’s custom rules are always re-evaluated against the cached result, so rule-based blocking is applied without triggering a new SMTP handshake. When an active inline blocking rule is present (e.g. blockFree: true), the cache is bypassed entirely and a fresh SMTP check is performed.

Fast Check deduplication (5 seconds):

To prevent duplicate charges from the widget firing multiple times (e.g. on both keystroke debounce and field blur), Fast Check results are deduplicated within a 5-second window per email and integration. If the same email is submitted again within that window, the cached result is returned and no credit is deducted. When an active blocking rule is present (e.g. blockFree: true), deduplication is bypassed so that rule changes take effect on the very next request rather than waiting out the window.

Free widget (no site key):

If you use the widget without a siteKey, no credits are charged and no results are logged. The widget provides a basic real-time check without contacting your integration endpoint.

When credits run out:

If your account has no remaining credits, verification requests return an error and form submission is blocked — the widget shows the service_unavailable message by default. No partial or silent failures occur. Top up your credits from the dashboard to restore normal operation.