← ClaudeAtlas

email-enrichmentlisted

LeadMagic email finder, email validation, personal email, and B2B Profile to email enrichment. Use when finding or validating a work email, finding a personal email, converting a B2B Profile URL to an email, or converting an email to a B2B Profile via REST or MCP.
LeadMagic/leadmagic-skills · ★ 0 · AI & Automation · score 78
Install: claude install-skill LeadMagic/leadmagic-skills
# LeadMagic — Email enrichment Auth: `X-API-Key: $LEADMAGIC_API_KEY` → `https://api.leadmagic.io`. Never echo the key. ## Which endpoint? | Goal | Endpoint | Credits | Rate/min | |---|---|---|---| | Validate an email | `POST /v1/people/email-validation` | 0.25 (conclusive only) | 5,000 | | Work email from name + company | `POST /v1/people/email-finder` | 1 (free on miss) | 5,000 | | Personal email from profile URL | `POST /v1/people/personal-email-finder` | 2 (free on miss) | 5,000 | | B2B Profile URL → work email | `POST /v1/people/b2b-profile-email` | 5 (free on miss) | 1,500 | | Email → full B2B Profile | `POST /v1/people/b2b-profile` | 10 | 1,500 | Cheapest-first ladder: find (1) → personal (2) → profile→email (5) → email→profile (10). Validation (0.25) is a separate lane for emails the user brought from elsewhere. **Every email a finder returns is already validated — always a good email; never chain a finder into validation.** If you already hold a profile URL and only need profile *fields*, use `profile-search` (1) — not `b2b-profile` (10). ## Field contract (forgiving on purpose) - **email-finder** needs the *person* (`first_name`+`last_name`, `full_name`, **or** a person `profile_url`) AND the *company* (`domain`/`company_domain`/`website`/`url` or `company_name`). CamelCase and common CRM aliases are accepted; `null` values are treated as omitted. - **Profile-URL endpoints** take `profile_url` (common CRM synonym keys are accepted); full URL or bare slug — `/in