Concepts
Emails & verification
enrich_rows finds a work email for each lead and checks it's deliverable, writing the results back into the table. You only pay for what it finds.
Docs menu
What a row needs
A first or last name (first_name, last_name) and the company's domain, website or, failing those, its company name. Rows from people search already have all of it. To only verify emails you already have, the row needs an email.
Reading the results
Three columns are added to the table:
| Column | Holds |
|---|---|
| The work email found. | |
| email_certainty | How sure the match is: ultra_sure, very_sure, probable (deliverability unconfirmed), or not_found and missing_input when there was nothing to find or not enough to search with. |
| email_verification | The verification result, e.g. ultra_sure or undeliverable. |
Emails found as ultra_sure or very_sure count as verified already, so they aren't verified again or charged twice.
What gets sent to
Enrolling a lead in a sequence skips emails marked undeliverable, but not probable ones. To send only to verified addresses, enroll with a filter, e.g. {"email_certainty": "ultra_sure"}.
In Claude Code
› Find and verify emails for the Fintech CTOs table, then enroll only the very_sure and ultra_sure ones.
Batches and cost
Per call
Up to 50 rows
25 by default, about 3 seconds a row. It returns how many remain; your agent calls again until 0.
Verification
1 credit
Only for emails that aren't verified already.
Rows already marked not_found or missing_input are skipped next time unless you ask to overwrite them. A row that hit an error is left as it was and retried on the next call. The CLI loops until done with pnpm meerko enrich <tableId> --all.