Use bulk or API-driven jobs to prepare email records, eliminate obvious waste, and return a normalized validity outcome without making unsupported inbox-delivery promises.
The verified upstream capability is an email validity check. Public copy should describe that signal accurately rather than claim SMTP delivery, inbox placement, spam-trap detection, or mailbox ownership unless those capabilities are separately implemented and verified.
Accept email data in supported bulk workflows.
Preflight formatting problems and exact duplicates before paid processing.
Return the configured email-validity outcome in a first-party schema.
Preserve job history, checked time, and export context.
Use validity as one quality layer inside a broader customer-data process.
Reduce obviously invalid or duplicated email values before enrichment, migration, or outreach.
Flag malformed or low-quality email input before it becomes a permanent record.
Audit email columns before importing them into a new CRM or data warehouse.
Recheck selected segments when freshness or source quality matters.
Before the job runs, users should see uploaded rows, invalid-format rows, exact duplicates, eligible cache hits, fresh checks required, and the maximum frozen quote.
No hidden provider terminology in the browser.
No generic “real-time” claim when the underlying signal or cache behavior does not justify it.
Visible freshness metadata on cached outcomes.
Results should be useful to operations teams as well as developers.
CSV/JSON-oriented normalized outputs.
External row IDs retained where supplied.
Outcome fields documented in the public API reference.
Webhook or job-status delivery for automated workflows.
No. The current product page should describe email validity only. Inbox placement and deliverability depend on many factors outside this validation signal.
Yes. The product is designed around asynchronous bulk jobs with preflight and export.
Exact duplicates are identified during preflight so the customer can see the effective job composition before confirmation.
The customer API exposes first-party job and result resources; use the API documentation for the current contract.
Use descriptive internal links so users and search engines can understand how these topics connect.
Start with a preflight, review duplicates, cache eligibility, fresh checks, and the frozen maximum quote.