US Employer Benefit Plans — Form 5500 🇺🇸

foXLabs US lead series: USPTO trademarks · FMCSA carriers · Insurance producers · Federal contractors

🎉 Turn DOL Form 5500 filings into clean, structured employer benefit-plan data — no login, no API key, one row per plan, with the sponsor (EIN), plan type, participant count and plan assets. Built for B2B sales, lead generation, KYB / compliance and market-research teams.

🔍 What is the US Employer Benefit Plans — and when should you use it?

Give this actor employer names or EINs and it returns matching benefit plans from US Department of Labor Form 5500 filings (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 US employer company list for outreach; formation / status monitoring; or a canonical registry record for KYB and due diligence.

Use something else when: you need a company’s commercial firmographics — Form 5500 is benefit-plan data (participants, assets), not a company registry.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/us-employer-benefit-plans.

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 US employer company records using the Apify Actor `foxlabs/us-employer-benefit-plans`.
Input: `year`, `states`, `industryCodes`, `keyword` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"year":"2023","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-employer-benefit-plans.md.

📋 Overview

Everything you need to turn US Department of Labor Form 5500 filings (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 companies 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-employer-benefit-plans/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"year":"2023","maxResults":1000}'

🚀 Getting Started (3 steps)

1. Choose your targets — employer names or EINs.
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

{"year":"2023","maxResults":1000}

Field	Type	Description
year	string	Which Form 5500 filing year to pull. Filings arrive up to ~10 months after year-end, so the most complete recent year is usually 2 years back.
states	array	Keep only employers in these US states — 2-letter codes (e.g. ["CA", "NY", "TX"]). Leave empty for all states.
industryCodes	array	Keep only employers whose business code starts with one of these NAICS prefixes. 2 digits = sector (e.g. "62" health care, "54" professional services, "23"…
keyword	string	Keep only employers whose name contains this text (case-insensitive). Example: "hospital", "bank", "acme". Leave empty to browse by the other filters.
planSize	string	Which filing dataset(s) to read: the Form 5500 (large-plan form), the Form 5500-SF (small-plan form), or both. Note: the output planSize field is measured from…
planType	string	Pension = retirement plans (401(k), defined benefit). Welfare = health, life, disability & other benefits. "Any" returns both.
minParticipants	integer	Keep only plans with at least this many participants — a proxy for employer headcount. Leave empty for no minimum.
maxParticipants	integer	Keep only plans with at most this many participants. Leave empty for no maximum.
minAssets	integer	Keep only plans reporting at least this much in total end-of-year assets. Assets come directly from 5500-SF filings and via the Schedule H join for large (Form…
onlyWithPhone	boolean	Return only employers that list a sponsor phone number (≈99% do). Useful for call-ready lead lists.
maxResults	integer	Maximum number of employer/plan records to return.

📤 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
sponsorName	Sponsor Name
dbaName	Dba Name
ein	Ein
phone	Phone
address	Principal address
city	City
state	State / province
zip	Zip
businessCode	Business Code
industry	Industry sector as published by the source — not a NACE or SIC code
planName	Plan Name
planNumber	Plan Number
planEntityType	Plan Entity Type
planEffectiveDate	Plan Effective Date
isPensionPlan	Is Pension Plan
isWelfarePlan	Is Welfare Plan
benefitCodes	Benefit Codes
participants	Participants
activeParticipants	Active Participants
totalAssets	Total Assets
totalAssetsFormatted	Total Assets Formatted
assetsSource	Assets Source
planSize	Plan Size
formType	Form Type
ackId	Ack Id
planYear	Plan Year
filingDate	Filing Date

💼 Use cases

1. Benefits / insurance prospecting — target employers by plan size and assets. Input: employer names. Output: plans + participants + assets. Use: a ranked prospect list.

2. Retirement-plan intelligence — size an employer’s benefit plans. Input: EINs. Output: plan financials. Use: qualify an account.

3. KYB / verification — verify an employer’s Form 5500 filing. Input: the EIN or name. Output: the canonical 5500 record. Use: confirm plan existence.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/us-employer-benefit-plans').call({"year":"2023","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-employer-benefit-plans').call(run_input={"year":"2023","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 Department of Labor Form 5500 filings (official open data).

What do I search by? Employer names or EINs.

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

What plan data is included? The sponsoring employer (EIN), plan type and year, participant count and plan assets from the Form 5500 filing.

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 a public government business registry published as open data. Results can still contain personal data (e.g. a registered agent’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.2.13 — 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: {"year":"2023","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.2 — 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 Department of Labor Form 5500 filings (official open data) by name or registry ID.