email-enrichment
Skill0 starsChanged 4 months agoMITView on GitHub
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.
- Reads credentials
- Sends data out
1 other project uses a version of this.
Adopted by
Most recently taken up by
- crustdata/skillstheir own version, first seen Sep 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- crustdata/skills★ 11same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- ads-intelligenceSkill
- analytics-observabilitySkill
- api-auth-creditsSkill
- bulk-jobsSkill
- company-enrichmentSkill
- company-searchSkill
- connect-leadmagicSkill
- job-searchSkill
- jobs-hiring-intentSkill
- leadmagicSkill
- mcp-integrationSkill
- outbound-recipesSkill
- people-enrichmentSkill
- people-searchSkill
- sheetsSkill
The file
Files
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. Email Finder returns a validation result with the address; inspect that result rather than immediately buying a duplicate validation. Delivery can still change over time. 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 personprofile_url) AND the company (domain/company_domain/website/urlorcompany_name). CamelCase and common CRM aliases are accepted;nullvalues are treated as omitted. A B2B person profile URL pasted into a name field is remapped toprofile_urlinstead of rejected. - Profile-URL endpoints take
profile_url(common CRM synonym keys are accepted); full URL or bare slug —/in/{username}forms are normalized. Company pages (/company/…) are rejected here; use Company Search for those. - b2b-profile accepts
work_email,personal_email, or plainemail(maps to work_email). - Names are sanitized (credentials, emojis, trailing digits stripped) but multi-person strings, bios, and company names in name fields are rejected with a 400 explaining the fix.
Examples
# Find
curl -sS -X POST "https://api.leadmagic.io/v1/people/email-finder" \
-H "X-API-Key: $LEADMAGIC_API_KEY" -H "Content-Type: application/json" \
-d '{"first_name":"Jane","last_name":"Doe","domain":"acme.com"}'
# Validate
curl -sS -X POST "https://api.leadmagic.io/v1/people/email-validation" \
-H "X-API-Key: $LEADMAGIC_API_KEY" -H "Content-Type: application/json" \
-d '{"email":"person@example.com"}'
# Profile URL → email
curl -sS -X POST "https://api.leadmagic.io/v1/people/b2b-profile-email" \
-H "X-API-Key: $LEADMAGIC_API_KEY" -H "Content-Type: application/json" \
-d '{"profile_url":"in/janedoe"}'Rules
- Public email-validation statuses are exactly
valid,invalid, andunknown. Validate emails sourced OUTSIDE LeadMagic before every send (recipe:outbound-recipesskill, "List hygiene"). Send onlyvalid; catch-all and other unverifiable outcomes areunknown, never a fourth status or send-ready. Finder-returned emails are already validated — skip re-validation. - A miss is free but final for that input — don't resubmit the identical request hoping for a different answer.
- Lists ≥ 50 rows → bulk (
bulk-jobsskill) withproduct: "email_finder"/"email_validation"; billed per successful row. - MCP equivalents:
find_work_email,validate_work_email,find_personal_email,b2b_profile_to_work_email,email_to_b2b_profile.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

