Real-time syntax and domain checks

Email Verifier Api checks an address's format, domain, and mail server response the moment it's submitted, returning a deliverability result the calling system can store. A Beam agent performs this check when a new address enters a signup or import flow, records the result against the contact, and blocks addresses the API marks as invalid or non-existent from moving further into the workflow. Addresses returned as risky rather than clearly invalid, catch-all domains or full inboxes, are held for a person to decide whether to keep them. The agent never deletes a contact outright based on one check.

Bulk list checking

Email Verifier Api accepts a batch of addresses and returns a status for each one once processing finishes. A Beam agent submits an approved list, such as an import from a signup form or spreadsheet, waits for the batch result, and updates each contact record with its status so the sending tool downstream can act on it. Addresses the API can't resolve within its usual timeframe, or a batch where an unusually high share comes back invalid, are flagged for a person to check before the list is used for a send. Nothing from that batch is removed automatically.

Role and disposable address flags

Email Verifier Api distinguishes a personal address from a role account, like support@ or info@, and from disposable or throwaway domains. A Beam agent applies the account's approved rule for each type, such as keeping role addresses for record purposes but holding disposable ones out of marketing sends, and updates the contact's status accordingly. Where an address matches more than one flag, a role account on a domain also marked disposable, the agent leaves the decision to a person rather than picking a rule to apply. No contact is removed from a list without that check passing first.