agentleFS
LeadMagicLeadMagic/leadmagic-skills/skills/email-enrichment/SKILL.md

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

The file

Files
SKILL.md

LeadMagic — Email enrichment

Auth: X-API-Key: $LEADMAGIC_API_KEY → https://api.leadmagic.io. Never echo the key.

Which endpoint?

GoalEndpointCreditsRate/min
Validate an emailPOST /v1/people/email-validation0.25 (conclusive only)5,000
Work email from name + companyPOST /v1/people/email-finder1 (free on miss)5,000
Personal email from profile URLPOST /v1/people/personal-email-finder2 (free on miss)5,000
B2B Profile URL → work emailPOST /v1/people/b2b-profile-email5 (free on miss)1,500
Email → full B2B ProfilePOST /v1/people/b2b-profile101,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 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. A B2B person profile URL pasted into a name field is remapped to profile_url instead 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 plain email (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, and unknown. Validate emails sourced OUTSIDE LeadMagic before every send (recipe: outbound-recipes skill, "List hygiene"). Send only valid; catch-all and other unverifiable outcomes are unknown, 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-jobs skill) with product: "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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.