Install Jentic One Beta

Connect the LeadMagic API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LeadMagic API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fleadmagic.io%2Fleadmagic" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fleadmagic.io%2Fleadmagic" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with LeadMagic API.

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

GET STARTED

Start building with LeadMagic API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LeadMagic API for, with concrete tasks.

★ 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.

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.

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.

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.

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

90 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using LeadMagic API through Jentic.

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.

LeadMagic API

AI ReadinessNon-Ready (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact EnrichmentapiKey (X-API-Key header)90 EndpointsREST

For 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.

Use for: I need to find the work email for Jane Doe at acme.com, Check whether this email address is valid before I send to it, Find the mobile number for this LinkedIn profile, Get the funding history and competitors for stripe.com

Not supported: 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.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4

50%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

32%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

55%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: B+Signals: 4

35%

Description Coverage

Coverage of descriptions across API elements.

84%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

87%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LeadMagic API to your agent

Capabilities

Start building with LeadMagic API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

LeadMagic API

Jentic AI Readiness Score

LeadMagic API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness