canonical: https://jentic.com/apis/leadmagic.io/leadmagic # LeadMagic API The LeadMagic API finds and verifies B2B contact data: it locates a work email from a person's name and company domain, validates an email address, finds mobile numbers and personal emails from a profile URL, and turns an email back into a B2B person profile. On the company side it returns company profiles, funding, competitors, technographics, and lookalike companies, finds employees or a specific role at a company, detects job changes, and searches job postings and the ads a company runs on Google, Meta, and B2B channels. Larger lists run through bulk jobs and mixed-product batches with cost previews, credit budgets, suppression lists, and usage analytics. ## For AI agents Find and validate work emails, mobile numbers, and B2B profiles, enrich companies with funding, competitors, and technographics, search people, jobs, and company ads, and run bulk enrichment jobs. ## Scope Does not handle sending emails, running outreach sequences, CRM record storage, or ad campaign management. Use for finding, validating, and enriching B2B contact and company data only. ## Capabilities - Find a person's work email from first_name, last_name, and domain or company_name, and validate any email address before sending - Look up a mobile number or personal email from a profile_url, and turn a work_email into a full B2B person profile - Enrich a company by domain with its profile, funding history, competitors, and the technologies it uses - Find people at a company by job_title with the role finder, or list employees with the employee finder - Detect whether a contact has changed jobs since you last saw them from their profile_url and old company - Search job postings by title, location, and seniority, and see the ads a company runs on Google and Meta - Submit bulk enrichment jobs from rows, CSV, or a fileUrl, preview batch cost, and cap spend with credit budgets ## Use cases ### Agent-run prospect research through Jentic An AI sales assistant preparing outreach can find the right person at a target account with the role finder, get their work email with the email finder, and validate it before it goes into a sequence. Through Jentic the agent finds each LeadMagic operation by intent and the X-API-Key credential is injected at execution time, and a rule can keep the agent to lookups so it cannot submit bulk jobs that spend credits in volume. Example prompt: Call POST `/v1/people/role-finder` with company_domain 'acme.com' and job_title 'VP Marketing', then POST `/v1/people/email-finder` with the returned name and domain, then POST `/v1/people/email-validation` with the found email ### Email finding and validation Bounced emails hurt sender reputation and waste outreach. LeadMagic finds a work email from a name plus a company domain, company name, or profile URL, and its email validation operation checks any address before it is used, so lists can be built and cleaned in the same flow. Example prompt: Call POST `/v1/people/email-validation` with email 'jane.doe@acme.com' and only add the contact to the campaign if the result is valid ### Company intelligence for account research Account executives want context before a call: who funds the company, who it competes with, and what software it runs. LeadMagic returns funding, competitors, and technographics for a company domain, and the lookalike search finds similar companies to expand a target account list. Example prompt: Call POST `/v1/companies/technographics` with company_domain 'acme.com' and POST `/v1/companies/company-funding` with company_domain 'acme.com', then summarise the stack and last funding round ### Bulk list enrichment with spend controls Enriching a CRM export one record at a time is slow and hard to budget. LeadMagic bulk jobs take a product with rows, CSV, or a fileUrl, can be validated first and approved or cancelled through review, and expose results as JSON or CSV. Credit budgets with max_credits and alert thresholds, plus suppression lists of emails to skip, keep large runs inside a set spend. Example prompt: Call POST `/bulk/validate` with product 'email_finder' and the rows from the export, then POST `/bulk/submit` with the same payload and poll GET `/bulk/jobs/{jobId}` until it completes ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/people/email-finder` | Find a work email | | POST | `/v1/people/email-validation` | Validate an email address | | POST | `/v1/people/mobile-finder` | Find a mobile number | | POST | `/v1/companies/company-search` | Look up a company | | POST | `/v1/companies/technographics` | Get company technographics | | POST | `/v3/people/search` | Search people | | POST | `/bulk/submit` | Submit a bulk job | | GET | `/v1/credits` | Check credits | ## Key resources - **People** — Email finder and validation, personal email and mobile finders, profile lookups, role and employee finders, job change detection, and people search - **Companies** — Company search, funding, competitors, technographics, and lookalike companies - **Jobs and ads** — Job posting search with filter helpers, and Google, Meta, and B2B ad searches by company - **Bulk and batch** — Bulk job submission, review, progress, and results; mixed-product batches, cost previews, budgets, and suppression lists - **Credits and analytics** — Credit balance, usage summaries, product breakdowns, and daily metrics ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 61 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 38 / 100 - Developer Experience & Jentic Compatibility: 72 / 100 - AI-Readiness & Agent Experience: 68 / 100 - Agent Usability: 87 / 100 - Security: 50 / 100 - AI Discoverability: 72 / 100 - **View full report:** https://jentic.com/apis/leadmagic.io/leadmagic/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring LeadMagic by hand means carrying the X-API-Key header, handling per-endpoint 429 limits, and choosing between single lookups, bulk jobs, and mixed-product batches across a large surface. Through Jentic you install once, import LeadMagic from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** LeadMagic carries the person or company being looked up in the request body, so rules bound which operations your agent may call, not which people or companies it researches. Bulk jobs, budgets, and suppression lists carry their ids in the URL path (`/bulk/jobs/{jobId}`, `/v1/batch/suppression-lists/{listId}`), so those operations can be pinned to one job or list. You choose the operations it may call, so spend-heavy or destructive ones like bulk submission or budget deletion are not included unless you add them. - **Credential handling:** Your LeadMagic API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find a work email' or 'get company technographics', and Jentic returns the matching LeadMagic operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Hunter API** — Email finder and verifier built around company domains - **Apollo API** — B2B contact database with sales engagement sequences - **Clearbit API** — Company and person enrichment from a domain or email - **ZeroBounce API** — Dedicated email validation and deliverability scoring ## FAQ ### Is there a LeadMagic MCP server? You don't need an MCP server to give your agent the LeadMagic API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. With a large surface like this one, operations are discovered on demand instead of loading every tool definition into your agent's context. ### What authentication does the LeadMagic API use? Per its OpenAPI spec, the LeadMagic API authenticates with an API key in the X-API-Key header, and the spec notes the header name is case-insensitive. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context. ### Can I find someone's work email with the LeadMagic API? Yes. POST `/v1/people/email-finder` accepts first_name and last_name or full_name, together with a domain, company_name, or profile_url. Follow it with POST `/v1/people/email-validation`, which takes a single email, to check the address before you send. ### What are the rate limits for the LeadMagic API? Per the OpenAPI spec, each endpoint has its own requests-per-minute limit and exceeding it returns 429 Too Many Requests. The spec does not list the per-endpoint values and notes that fair use rules can lead to throttling; check https://leadmagic.io and its fair use terms at https://leadmagic.io/legal/terms for current limits. ### How do I enrich a company through Jentic? Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the LeadMagic API from the directory, and store your API key. Your agent then searches for 'enrich a company by domain' and Jentic returns POST `/v1/companies/company-search`, which accepts company_domain, company_name, or profile_url. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### How do I control credit spend on large LeadMagic jobs? Preview a mixed-product batch with POST `/v1/batch/preview-cost` before submitting it, and create a credit budget with POST `/v1/batch/budgets` using scope, scope_value, and max_credits, plus an optional alert_threshold_pct and alert_email. Bulk jobs can also be approved or cancelled through POST `/bulk/jobs/{jobId}/review.` ### Can I limit what my agent is allowed to do with the LeadMagic API? Yes. For an outreach assistant, write a rule that allows POST `/v1/people/email-finder`, POST `/v1/people/email-validation`, and GET `/v1/credits`: the agent can find and check emails and see its remaining credits, but cannot submit bulk jobs, change budgets, or edit suppression lists, and every call it makes is logged.