US Insurance Producer Leads 🛡️

foXLabs US lead series: USPTO trademarks · FMCSA carriers · Employer benefit plans · Federal contractors

🎉 Turn state producer licenses into clean, structured lead data — no login, no API key, one row per producer, with the license number, lines of authority, status, state and contact. Built for insurance recruiting, IMOs and B2B sales.

🔍 What is the US Insurance Producer Leads — and when should you use it?

Give this actor producer names or license numbers and it returns matching producers from US state insurance-producer license records (official open data) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: a insurance producer company list for outreach; formation / status monitoring; or a canonical registry record for KYB and due diligence.

Use something else when: you need carrier or company financials — this is producer-license data.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/us-insurance-producer-leads.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull insurance producer company records using the Apify Actor `foxlabs/us-insurance-producer-leads`.
Input: `preset`, `datePreset`, `issueDateFrom`, `issueDateTo` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"preset":"newly_licensed","maxResults":1000}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/us-insurance-producer-leads.md.

📋 Overview

Everything you need to turn US state insurance-producer license records (official open data) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole registry, one call — name or ID in, matching producers out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~us-insurance-producer-leads/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"preset":"newly_licensed","maxResults":1000}'

🚀 Getting Started (3 steps)

1. Choose your targets — producer names or license numbers.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"preset":"newly_licensed","maxResults":1000}

Field	Type	Description
preset	string	Start here — each preset is a ready-made filter combination. 'Newly licensed' finds producers whose FIRST-EVER Florida licence was issued inside the date window…
datePreset	string	Which licence-issue dates count. With the 'Newly licensed' preset this is tested against the producer's first-ever licence. Defaults to the last 90 days for…
issueDateFrom	string	YYYY-MM-DD, e.g. 2026-01-01. Only used when Date range = Custom.
issueDateTo	string	YYYY-MM-DD. Only used when Date range = Custom. Leave empty for 'up to today'.
firstTimeOnly	boolean	ON (default for 'Newly licensed'): the date window must contain the producer's very first Florida licence, so you get genuine new entrants. OFF: any licence…
licenseCategories	array	Plain-English groupings of Florida's 78 licence class codes. Leave empty for every class.
licenseTypeCodes	array	Raw Florida TYCL codes, e.g. 0215, 0620, 0814. Combined with the categories above (a licence matching either is kept). Leave empty unless you need a class the…
licenseStatus	string	The source file only contains valid licences: 99.98% are VALID and 0.02% are VALID - PROBATION (measured on 1.19 M rows). Use 'Probation only' to isolate that…
residentOnly	boolean	ON keeps resident licensees only. Roughly 59% of Florida licences are held by non-residents living in other states — useful reach, but resident producers are the…
counties	array	e.g. Dade, Broward, Hillsborough, Orange. 'Miami-Dade' is accepted and mapped to the register's spelling ('Dade'). Note: the county column is only populated for…
cities	array	Exact business-address city names, e.g. MIAMI, ORLANDO, TAMPA. Case-insensitive. Leave empty for all.
businessStates	array	Two-letter codes filtering the business address, e.g. FL, TX, NY. Useful to target non-resident Florida licensees living in a particular state. Leave empty for all.
appointmentFilter	string	Joins the state's active-appointment files (~1 GB, adds time to the run) and can filter on the result. 'No active appointment' is the recruiting list: licensed…
requireEmail	boolean	Drop producers without a valid email. Coverage is 99.99% on the raw file, so this rarely removes anything.
requirePhone	boolean	Drop producers without a usable 10-digit business phone (placeholder numbers such as 0000000000 never count as filled).
groupByLicensee	boolean	ON (default): one row per person, with all their licence classes in a nested list — you are not billed for the same producer 1.27 times. OFF: one row per licence…
maxResults	integer	Hard cap on output rows. Set to 0 for unlimited — the full file holds ~937,000 producers across ~1.19 M licence rows.
maxRunSeconds	integer	Stop after this many seconds and keep the rows collected so far, instead of being cut off by the run timeout and losing them. 0 = no budget. Run length…

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
fullName	Full Name
email	Email
businessPhone	Business Phone
npn	Npn
licenseNumber	License Number
licenseTypes	License Types
firstLicenseDate	First License Date
licenseClassCount	License Class Count
residencyType	Residency Type
businessCity	Business City
businessCounty	Business County
businessState	Business State
hasActiveAppointment	Has Active Appointment
activeAppointmentCount	Active Appointment Count
dataAsOf	Data As Of

💼 Use cases

1. Agency recruiting — find licensed producers by state and line. Input: producer names. Output: producers + lines + status. Use: a recruiting list.

2. Compliance checks — verify a producer’s license status. Input: license numbers. Output: status + lines. Use: a compliance result.

3. B2B sales — target active producers in a state. Input: producer names. Output: producers + contact. Use: a lead list.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/us-insurance-producer-leads').call({"preset":"newly_licensed","maxResults":1000});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/us-insurance-producer-leads').call(run_input={"preset":"newly_licensed","maxResults":1000})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads US state insurance-producer license records (official open data).

What do I search by? Producer names or license numbers.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

What license data is included? License number, lines of authority, status, issue/expiry, state and contact where the state publishes it.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResults, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads public US state insurance-producer license records. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.15 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"preset":"newly_licensed","maxResults":1000}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from US state insurance-producer license records (official open data) by name or registry ID.