LeadMagic provides people, company, jobs, advertising, and enrichment data for sales and recruiting workflows.
Add a non-empty plaintext email list to one owned suppression list; LeadMagic stores only normalized SHA-256 hashes. Use the exact list_id captured in the same create lifecycle and only addresses intentionally owned by that workflow.
Create a persistent credit budget that caps spend for one LeadMagic scope. Record the returned id so the owned budget can be updated or deleted later.
Create an owned suppression list from a unique list_id and non-empty plaintext email list. LeadMagic hashes emails server-side. Capture the returned list_id, use only that exact ID for subsequent reads or mutations, and always delete the owned list at the end of the lifecycle.
Synchronously export up to 5,000 matching jobs. At least one search filter is required. This route is credit-metered, but LeadMagic does not publish an exact rate. The limit defaults to 1 and bounds result count, not guaranteed credit exposure; use credits_consumed as finalized spend.
Permanently delete one credit budget. This is an irreversible teardown action: use only the exact budget ID captured from Create Credit Budget in the same owned lifecycle, and never delete a budget discovered by listing workspace data.
Permanently delete an entire suppression list and its stored hashes. This is an irreversible teardown action: use only the exact list_id captured from Create Email Suppression List in the same owned lifecycle, never a pre-existing list.
Check whether a person has changed jobs relative to an expected company. A resolved check costs 3 credits; PROFILE_NOT_FOUND costs 0 credits.
Download all result rows for an owned bulk job as a CSV file. Use only a jobId captured from the same submission chain. The streamed download is offloaded and fails if it exceeds the documented 50 MiB bulk source-size bound.
Call POST /v1/companies/company-search to enrich one company from its domain, name, or business profile identifier. A successful enriched-company result costs 1 credit; use credits_consumed as the finalized spend.
Call the distinct documented POST /v3/companies/enrich alias. Prefer SEARCH_COMPANIES for new integrations. Returns one cursor-controlled page. This route remains ordinarily metered even when browsing routes are unmetered; LeadMagic does not state an exact alias-specific charge, so use credits_consumed as finalized spend.
Find competitors from a company domain, profile, or name. A successful competitor list costs 5 credits.
Find up to 10 employees at one company, returning names, titles, locations, and professional profile URLs. Provider documentation conflicts between 0.05 and 1 credit per returned employee, so treat 1 credit per result as the exposure bound and use credits_consumed as finalized spend.
Call POST /v1/jobs/jobs-finder to find jobs with the LeadMagic V1 filters. Each returned job costs 1 credit; an empty result costs 0 credits. per_page is capped at 50.
Find similar companies from a seed domain, name, or description. The OpenAPI contract documents a flat 5-credit charge for a non-empty result and no charge when empty; another provider surface says 1 credit, so use credits_consumed as the finalized spend.
Find one person's mobile phone number from a professional profile URL or known email. A found mobile number costs 5 credits; no result is free. Exactly one person is processed per call.
Find one person by job title at a specified company. A successful match costs 2 credits; rely on credits_consumed as finalized spend. The response can contain personal identity and professional profile data.
Find one person's personal email addresses from a professional profile URL or identifier. A successful result costs 2 credits. Personal email addresses are sensitive personal data; use this tool only for a lawful, authorized purpose.
Find one person's work email from their name and company domain or name. A found valid email costs 1 credit; no result is free. Exactly one person is processed per call.
Find one person's work email from a professional profile URL or slug. LeadMagic's published sources conflict on whether a successful result costs 1 or 5 credits; treat 5 credits as the maximum documented exposure and use credits_consumed as finalized spend.
Return the connected workspace's available credits, API-key permission summary, current rate limits, and today's usage. This read is free.
Get documented lifetime account request, credit, product, success, and latency statistics, optionally restricted to a date range. This free analytics route was not individually live-probed during the build.
Get LeadMagic credit consumption history with a daily breakdown.
Get documented daily request, credit, latency, and error metrics for the last 1 to 90 days. This free analytics route was not individually live-probed during the build.
Get the documented per-product request and credit breakdown for one date. This free analytics route was not individually live-probed during the build.
Get per-product LeadMagic usage with request, credit, and success metrics.
Get daily LeadMagic usage with request, credit, and chargeable-rate totals.
Get full details for a specific B2B ad from its library URL, detail path, or numeric ID. A successful full-details lookup costs exactly 2 credits; use credits_consumed as finalized spend.
Find one person's professional profile from a supplied work or personal email. A found complete profile costs 10 credits. Email addresses and matched profile data are personal data; submit and use them only for a lawful, authorized purpose.
Retrieve one person's professional profile, including employment, education, certifications, and honors, from a profile URL or slug. A found full profile costs 1 credit. Returned profile data is personal data; use it only for a lawful, authorized purpose.
Read status, progress, cost, and metadata for a mixed-product batch by its exact batch identifier. A missing synthetic identifier safely returns not found and does not mutate or spend credits.
Read aggregate usage and success metrics for a batch campaign. A syntactically valid missing identifier can be used for a safe, non-mutating not-found check.
Read aggregate batch usage and success metrics for one client UUID. An all-zero missing UUID is safe for a non-mutating not-found check.
Return the current bulk submission limits and supported operational features in a stable agent-facing shape. Service-internal host and deployment metadata are intentionally omitted.
Read status, progress, timestamps, and finalized credit usage for one bulk job. Pass a jobId captured from the same owned submission workflow; do not inspect an unrelated workspace job.
Return LeadMagic's compact progress snapshot for frequent polling of one bulk job owned by the connected workspace. This read does not start, stop, or restart processing.
Call POST /v1/companies/company-funding to get complete funding history and related company intelligence by domain or name. A successful funding result costs 4 credits.
Call the distinct documented POST /v3/companies/company-funding alias. Prefer SEARCH_COMPANIES for new integrations. Returns one cursor-controlled page. This route remains ordinarily metered even when browsing routes are unmetered; LeadMagic does not state an exact alias-specific charge, so use credits_consumed as finalized spend.
Call the distinct documented POST /v3/companies/funding alias. Prefer SEARCH_COMPANIES for new integrations. Returns one cursor-controlled page. This route remains ordinarily metered even when browsing routes are unmetered; LeadMagic does not state an exact alias-specific charge, so use credits_consumed as finalized spend.
Get a company's technology stack from its domain. A successful stack result costs 1 credit; use credits_consumed as finalized spend.
Check the connected LeadMagic workspace's current credit balance for free.
Read current limits, remaining credits, and exceeded state for every LeadMagic credit budget. This does not reserve or consume credits.
Validate the connected LeadMagic API key and check credit-service authentication status. This medium-confidence docs-only read has an undocumented response schema and billing behavior and was not live-probed.
Return one offset-controlled page of details and irreversible SHA-256 email hashes for one owned suppression list. Use only the exact list_id captured in the same create lifecycle, never auto-fetch pages, and continue only with the returned next_offset. Hashes cannot be converted back to plaintext emails.
Return the free job search dataset statistics through LeadMagic's exact job-board integration alias route.
Return the free filter catalogs used by job search, including countries, regions, job types, industries, company types, and seniority values. This helper consumes 0 credits.
Return free public coverage, freshness, and capability statistics for the LeadMagic Jobs Search index.
Return free cached coverage, capabilities, and top dimensions for selected LeadMagic search products. Requested product sections may be absent when unavailable. This helper costs 0 credits.
List delivery webhooks configured for one batch client. This read does not create, change, or invoke webhooks.
List existing organization-scoped client records used to segment batch work. This read does not create or modify clients.
List one bounded page of mixed-product batches for the connected organization. Continue only with the returned next_offset; this tool never auto-fetches additional pages.
Return one offset-controlled page of failed rows and error details for a bulk job owned by the connected workspace. This is read-only and never retries or restarts failed rows.
Return the append-only event log, newest first, for one bulk job owned by the connected workspace. Reading events does not alter the job lifecycle.
Return one bounded offset page of row-level JSON results for an owned bulk job. Use only a jobId captured from the same submission chain and pass next_offset back explicitly to continue; this tool never auto-fetches all rows.
Return one bounded offset page of bulk jobs owned by the connected account, newest first. Use next_offset to continue; this action never auto-fetches pages.
List all persistent credit budgets configured for the connected LeadMagic workspace, including identifiers needed for owned-budget lifecycle operations.
Read all suppression-list summaries for the connected workspace. This tool is for discovery only: never pass an ID from this result to a mutation or deletion; lifecycle writes must use the exact ID captured from a list created by that workflow.
List organization-level external enrichment provider configurations. LeadMagic redacts stored credentials from this read.
List the company type IDs accepted by the legacy V1 Jobs Finder API. No route-specific charge is documented; reported finalized spend should be treated as authoritative.
List the free country codes accepted by the legacy V1 Jobs Finder API. Use V3 catalogs or locations for V3 job search.
List the industry IDs accepted by the legacy V1 Jobs Finder API. No route-specific charge is documented; reported finalized spend should be treated as authoritative.
Autocomplete LeadMagic's broad-to-specific occupation taxonomy and return canonical IDs, labels, levels, and paths. This helper is free and consumes 0 credits.
List the free region IDs accepted by the legacy V1 Jobs Finder API. Use the exact returned IDs with V1 job searches.
Autocomplete companies or resolve an exact domain into canonical company IDs and card data for Job Search filters. This helper is free and consumes 0 credits.
Autocomplete countries, regions, states, and cities into canonical IDs for exact Job Search geo filters. This helper is free and consumes 0 credits.
Autocomplete role names into canonical occupation taxonomy IDs for Job Search filters. This helper is free and consumes 0 credits.
Autocomplete normalized job tags with tag-type and occupation taxonomy metadata for Job Search filters. This helper is free and consumes 0 credits.
Autocomplete searchable job title phrases with occupation taxonomy metadata for Job Search filters. This helper is free and consumes 0 credits.
List the job type IDs accepted by the legacy V1 Jobs Finder API. No route-specific charge is documented; reported finalized spend should be treated as authoritative.
Call the distinct documented POST /v3/companies/domain-lookup alias. Prefer SEARCH_COMPANIES for new integrations. Returns one cursor-controlled page. This route remains ordinarily metered even when browsing routes are unmetered; LeadMagic does not state an exact alias-specific charge, so use credits_consumed as finalized spend.
Call the distinct documented POST /v3/companies/lookup alias. Prefer SEARCH_COMPANIES for new integrations. Returns one cursor-controlled page. This route remains ordinarily metered even when browsing routes are unmetered; LeadMagic does not state an exact alias-specific charge, so use credits_consumed as finalized spend.
Pause a queued or running LeadMagic bulk job. This mutates processing state but is reversible with Resume Bulk Job. Use only a job ID owned by the connected workspace and intentionally selected for this lifecycle workflow.
Estimate the maximum credit cost and budget impact of an exact mixed-product batch payload. This is a free dry run: it does not submit work, reserve credits, or consume credits.
Force LeadMagic to refresh the connected workspace's credit cache from its database. This medium-confidence docs-only POST updates cached account state; its response schema and billing behavior are undocumented and it was not live-probed.
Irreversibly remove specific email suppressions from one owned list, allowing those addresses to be processed again. Use only the exact list_id captured in the same create lifecycle and the exact lifecycle-owned plaintext addresses previously added; never alter a pre-existing list.
Resolve friendly job-search companies, tags, occupation taxonomy, locations, and titles into canonical values. This helper returns no jobs and costs 0 credits.
Destructively restart a LeadMagic bulk job in full, for failed rows only, or from a zero-based row or shard. This irreversible lifecycle operation can repeat work and consume additional credits. Use only an intentionally selected job owned by the connected workspace; inspect its status and errors first.
Resume a paused LeadMagic bulk job. This mutates processing state and may continue the job's existing credit-consuming work. Use only a job ID owned by the connected workspace and intentionally paused in this workflow.
Resume or irreversibly cancel an owned bulk job. Use only a jobId captured from the same submission chain, choose a state-valid transition, and never mutate a pre-existing job discovered by listing workspace jobs.
Search for B2B ads by company domain or name. The exact charge is 1 base credit plus 1 credit per returned ad, with a minimum of 1 credit. Set limit to bound the per-ad portion; use credits_consumed as finalized spend.
Call the canonical POST /v3/companies/search route to search or look up companies by domain, name, website, professional profile URL, or company filters and return one cursor-controlled page. On the connected Starter plan, each search request costs 1 credit; eligible higher plans may be unmetered. The page limit is capped at 50.
Call the distinct legacy compatibility route POST /v1/companies/search. Prefer SEARCH_COMPANIES for new integrations. Returns one cursor-controlled page. Billing is 1 credit per search on metered plans and unmetered on eligible Search RPS plans; credits_consumed is the finalized spend.
Call the distinct documented POST /v3/companies/company-search alias. Prefer SEARCH_COMPANIES for new integrations. Returns one cursor-controlled page. Billing is 1 credit per search on metered plans and unmetered on eligible Search RPS plans; credits_consumed is the finalized spend.
Search for Google ads run by a company. Each returned ad costs exactly 1 credit and no results are free. The limit defaults to 1 to bound spend; use credits_consumed as finalized spend.
Call the canonical POST /v3/jobs/search route to search by title, company, location, taxonomy, tags, salary, seniority, date, and work arrangement, returning one cursor-controlled page. On the connected Starter plan, each returned job costs 1 credit and zero-result pages are free. Eligible higher plans may be unmetered. The page limit is capped at 5, for a maximum exposure of 5 credits per call.
Call the distinct legacy compatibility route POST /v1/jobs/search; prefer POST /v3/jobs/search for new integrations. Returns one cursor page. Billing is 1 credit per search on metered plans and unmetered on eligible Search RPS plans.
Call the distinct legacy compatibility route POST /v2/jobs/search; prefer POST /v3/jobs/search for new integrations. Returns one cursor page. Billing is 1 credit per search on metered plans and unmetered on eligible Search RPS plans.
Search the distinct documented POST /v3/jobs-search alias and return one cursor-controlled page. On metered plans, each returned job can cost 1 credit; the page limit is capped at 5 credits of result exposure.
Call the distinct documented compatibility route POST /v3/job-search; prefer POST /v3/jobs/search for new integrations. Returns one cursor page. Billing is 1 credit per search on metered plans and unmetered on eligible Search RPS plans.
Search for Meta ads by company domain or name. Each returned ad costs exactly 1 credit and no results are free. The limit defaults to 1 to bound spend; use credits_consumed as finalized spend.
Call the canonical POST /v3/people/search route to search by company, title, role, free text, and contact availability, returning one cursor-controlled page without raw email or mobile details. On the connected Starter plan, each returned person costs 1 credit; zero results are free. The maximum base exposure is 10 credits per call.
Call the distinct legacy compatibility route POST /v1/people/search; prefer the canonical V3 route for new integrations. Returns one base-only cursor page and never requests raw contact details. Each returned person costs 1 credit on metered plans; zero results are free; maximum base exposure is 10 credits.
Call the distinct legacy compatibility route POST /v2/people/search; prefer the canonical V3 route for new integrations. Returns one base-only cursor page and never requests raw contact details. Each returned person costs 1 credit on metered plans; zero results are free; maximum base exposure is 10 credits.
Call the distinct compatibility route POST /v3/people/by-title; prefer the canonical route for new integrations. Returns one base-only cursor page and never requests raw contact details. Each returned person costs 1 credit on metered plans; zero results are free; maximum base exposure is 10 credits.
Call the distinct documented POST /v3/people/company-search alias. Prefer SEARCH_PEOPLE for new integrations. Returns one cursor page without raw contacts. Each returned person costs 1 base credit; zero results are free.
Call the distinct compatibility route POST /v3/people/contacts-by-title; prefer the canonical route for new integrations. Returns one base-only cursor page and never requests raw contact details. Each returned person costs 1 credit on metered plans; zero results are free; maximum base exposure is 10 credits.
Call the distinct compatibility route POST /v3/people/employees; prefer the canonical route for new integrations. Returns one base-only cursor page and never requests raw contact details. Each returned person costs 1 credit on metered plans; zero results are free; maximum base exposure is 10 credits.
Call the distinct documented POST /v3/people/full-search alias. Prefer SEARCH_PEOPLE for new integrations. Despite its route name, raw contacts stay disabled. Each returned base person costs 1 credit; zero results are free.
Call the distinct documented compatibility route POST /v3/people/icp-search; prefer POST /v3/people/search for new integrations. Returns one base-only cursor page and never requests raw contact details. Each returned person costs 1 credit on metered plans; zero results are free; maximum base exposure is 10 credits.
Call the distinct compatibility route POST /v3/people/lookalike; prefer the canonical route for new integrations. Returns one base-only cursor page and never requests raw contact details. Each returned person costs 1 credit on metered plans; zero results are free; maximum base exposure is 10 credits.
Call the distinct documented POST /v3/people/mixed-search alias. Prefer SEARCH_PEOPLE for new integrations. Returns one cursor page without raw contacts. Each returned person costs 1 base credit; zero results are free.
Call the distinct documented POST /v3/person/search alias. Prefer SEARCH_PEOPLE for new integrations. Returns one cursor page of base person data without raw contacts. Each returned person costs 1 base credit; zero results are free.
Create one asynchronous bulk enrichment job from exactly one input mode. This can consume credits for every processed row. Retain the returned jobId and use only that owned ID for follow-up reads or lifecycle changes.
Create a long-running local-leads bulk job. Every keyword-city combination becomes work and may consume credits. Retain the returned jobId and use only that owned ID for follow-up reads or lifecycle changes.
Create one asynchronous mixed-product enrichment batch. This can consume credits for every item: preview the exact payload first, keep the item count bounded, and supply an idempotency_key before submitting.
Update metadata or client association for an owned batch during its mutable window. Use only a product and batch_id captured from the same submitted batch; never mutate a batch discovered by listing workspace data.
Change the priority of a queued or running LeadMagic bulk job owned by the connected workspace. This mutates scheduling but does not restart the job or change which rows it processes.
Update one or more controls on a credit budget created and owned by the caller. Use only an id captured from that owned budget lifecycle; never modify a budget discovered incidentally in workspace listings.
Validate exactly one bulk input mode and its options without persisting or processing a job. This is a contract check, not a submission.
Check one email address for deliverability and return mail-server and company context. A definitive valid or invalid result costs 0.25 credits; an unknown result is free. Exactly one email is validated per call.
The LeadMagic integration connects your Dench AI CRM directly to LeadMagic, so agents can read and act on your LeadMagic data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
109 actions are available for agents to invoke on your behalf. Every call runs through LeadMagic's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find LeadMagic and click Connect — you'll authorize access through LeadMagic's own sign-in flow. No API keys or code required.
Ask an agent to use LeadMagic in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench LeadMagic integration connects your AI CRM to LeadMagic, so AI agents can work with your LeadMagic data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The LeadMagic integration currently exposes 109 actions, including Add Emails To Suppression List, Create Credit Budget, Create Email Suppression List, Create Job Search Export V3, Delete Credit Budget, and Delete Email Suppression List. Agents invoke them on your behalf from chat or from automations.
No. You connect LeadMagic from your Dench workspace using LeadMagic's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through LeadMagic's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the LeadMagic connection from your workspace settings at any time.