LeadMagic
Find an email, prove it is real, and find the mobile behind it.
LeadMagic is a contact enrichment tool, and one of the 53 tools hyreflow connects to Claude, ChatGPT and other AI assistants. Through hyreflow, an AI agent can run 13 actions, all of which look something up. Paid LeadMagic actions cost 0.1 to 5.5 credits per result or per request, from your hyreflow credit balance, so you need no LeadMagic account, though you can connect your own key.
LeadMagic covers the whole contact-finding job in one place: work emails, personal emails, mobile numbers, and validation on top. It also resolves a LinkedIn profile from an email address, and flags when someone has quietly changed jobs.
LeadMagic sits between the list and the outreach, and it validates on the way through, so nothing unverified reaches a sequencer.
What can you ask Claude or ChatGPT to do with LeadMagic?
With hyreflow connected, you ask for the outcome in plain language and the assistant runs LeadMagic for you. For example:
Which tools work well with LeadMagic?
In a hyreflow run, LeadMagic is most often paired with Wiza, SmartLead, Vincere and Apollo.
Which LeadMagic actions can an AI agent run through hyreflow?
Through hyreflow, an AI agent can run 13 LeadMagic actions, all of which look something up. Paid LeadMagic actions cost 0.1 to 5.5 credits per result or per request, from your hyreflow credit balance, so you need no LeadMagic account, though you can connect your own key.
| LeadMagic action | What it does | Cost through hyreflow |
|---|---|---|
| Company search | Looks something up | 0.6 credits per result |
| Email finder | Looks something up | 0.6 credits per result |
| Employee finder | Looks something up | 0.1 credits per result |
| Mobile finder | Looks something up | 2.8 credits per result |
| People search | Looks something up | 0.6 credits per result |
| Personal email finder | Looks something up | 1.1 credits per result |
| Profile search | Looks something up | 0.6 credits per result |
| Role finder | Looks something up | 1.1 credits per result |
| B2B profile | Looks something up | 5.5 credits per result |
| Company funding | Looks something up | 2.2 credits per result |
Show all 13 LeadMagic actions →
| LeadMagic action | What it does | Cost through hyreflow |
|---|---|---|
| Email validation | Looks something up | 0.2 credits per result |
| Job change detector | Looks something up | 1.7 credits per request |
| Technographics | Looks something up | 0.6 credits per result |
One credit is priced on the pricing page. The full price list for every tool is in the pricing tables.
Which hyreflow skills use LeadMagic?
56 hyreflow skills call LeadMagic as part of the run. A skill is a whole pipeline your agent already knows, end to end.
Ask the people you placed for referrals into a live role
use whenyou have years of placements in your database and no habit of asking those people who else is good
Find candidates who have said publicly that they are open to work
use whena role has to be filled fast and you want to start with the people who have raised a hand, without the open-to-work filter in LinkedIn Recruiter
Find more candidates like the best person you ever placed
use whenyou can point at one person and say more like this, faster than you can write the brief that describes them
Find the candidate one level below who is ready to step up
use wheneveryone who already holds the title is out of budget or not moving, and the realistic hire is someone one level below
Map a whole talent pool, including the half that is not looking
use whenthe role is hard, the obvious search is exhausted, and you need to prove to a client that you have covered the market
Run one candidate search across every people database at once
use whenone database keeps handing you the same names and you suspect the rest of the market is sitting in the others
How does an AI agent know how to use LeadMagic?
hyreflow ships a written playbook for LeadMagic, and the agent loads it before the first call. Auth, rate limits, what each call costs, which actions need your approval, and the mistakes worth avoiding. It is the difference between an agent that knows the tool and one that guesses at it.
Read the LeadMagic docs →Show the raw playbookwritten for the agent
WHAT/guardrails here; HOW in reference/endpoints.md + lib/leadmagic.py. Docs cached at reference/docs/leadmagic/raw/llms-full.txt.
Auth & config
- Base URL:
https://api.leadmagic.io - Auth: header
X-API-Key(LeadMagic → Settings → API). EnvLEADMAGIC_API_KEY; never hardcode. - Most endpoints are POST with a JSON body;
GET /v1/creditsis free.
Guardrails
- Credits are consumed per successful result.
get_credits()reads your own LeadMagic account and needs your own LeadMagic key; pilot one lookup before bulk, and run bulk row-by-row through a deterministic loop (not the agent per row).
Operations
People: email_finder, email_validation, personal_email_finder, mobile_finder, profile_search, b2b_profile (email→profile), role_finder, employee_finder, job_change_detector, people_search (v3). Companies: company_search, company_funding, technographics. Plus get_credits. Anything else (ads, analytics, jobs) → generic request().
Handoff
Enrichment layer: shortlist (Apollo/Exa) → LeadMagic for verified emails/phones + LinkedIn resolution → write to ATS (recruit-crm) / sequencer (instantly). Validate emails (email_validation) before any send.
Waterfall membership: personal_email_finder is a member of personal_email, mobile_finder of phone_enrichment, and profile_search of linkedin_profile.
Field notes (production experience)
Field-shape note: these are vendor-native operational notes. The client returns the raw vendor JSON and uses the method names in this file — read field shapes accordingly (no normalized-wrapper /
result.data.prefix).
- Cheap gates first: email validation, company search, jobs finder - escalate to email finder / mobile finder / profile search only when the target is worth it.
- Validation rule: accept
email_status == valid; treatcatch_allandunknownas unresolved unless risk is accepted. - Conservative on catch-all (many Google Workspace / corporate domains):
invalidwith a populatedmx_record+mx_providerusually means "mailbox not provable", not "won't deliver" - don't auto-discard; fall back to a second validator (ZeroBounce/BetterContact) first. - If pilot profile/phone quality is noisy, switch to a quality-first enricher before scaling.
- Run 1-row pilots; validate every email candidate; keep fallback chains explicit.
Callable surface — lib/leadmagic.py
Import: from lib.leadmagic import LeadMagic → instantiate LeadMagic() (reads key from env). Base: https://api.leadmagic.io. Generic passthrough: request(method, path, *, params, json).
b2b_profile(payload: dict) -> dict— POST /v1/people/b2b-profile — profile from an email (email -> LinkedIn profile).company_funding(payload: dict) -> dict— POST /v1/companies/company-funding — funding data for a company.company_search(payload: dict) -> dict— POST /v1/companies/company-search — find/enrich a company by domain/profile.email_finder(payload: dict) -> dict— POST /v1/people/email-finder — work email from first_name + last_name + domain/company_name.email_validation(email: str, **opts) -> dict— POST /v1/people/email-validation — deliverability/validation for an email.employee_finder(payload: dict) -> dict— POST /v1/people/employee-finder — list employees at a company.get_credits() -> dict— GET /v1/credits — current credit balance on your own LeadMagic account (needs your own LeadMagic key).job_change_detector(payload: dict) -> dict— POST /v1/people/job-change-detector — detect recent job changes.mobile_finder(payload: dict) -> dict— POST /v1/people/mobile-finder — mobile phone from profile_url, work_email or personal_email (no name+domain mode).people_search(payload: dict) -> dict— POST /v3/people/search — people search (v3).personal_email_finder(payload: dict) -> dict— POST /v1/people/personal-email-finder — personal email from a profile.profile_search(payload: dict) -> dict— POST /v1/people/profile-search — find/enrich a LinkedIn profile.role_finder(payload: dict) -> dict— POST /v1/people/role-finder — find the person in a given role at a company.technographics(payload: dict) -> dict— POST /v1/companies/technographics — tech stack for a company.
Questions about LeadMagic and hyreflow
Can I use LeadMagic inside Claude or ChatGPT?
Yes. hyreflow is a connector for Claude, ChatGPT and other AI assistants. Once hyreflow is connected, you ask for the outcome in plain language and the assistant calls LeadMagic for you. hyreflow exposes 13 LeadMagic actions this way.
Do I need my own LeadMagic account to use it with hyreflow?
No. hyreflow holds the LeadMagic account and bills each action from your hyreflow credits. If you already pay for LeadMagic, you can connect your own key instead, and hyreflow then charges no credits for those calls.
What does LeadMagic cost through hyreflow?
Paid LeadMagic actions cost 0.1 to 5.5 credits per result or per request, from your hyreflow credit balance, so you need no LeadMagic account, though you can connect your own key. hyreflow can show the cost of a paid action before it runs.
How do I connect LeadMagic to an AI agent over MCP?
Add the hyreflow MCP server to your assistant and sign in. hyreflow calls the LeadMagic API directly and exposes its actions as tools the assistant can run, so there is no separate LeadMagic server to install.
Put LeadMagic to work from one prompt
Connect hyreflow to Claude or ChatGPT and ask for the outcome. It reads the playbook above before it makes a single call.