SEC Enforcement Actions ⚖️

foXLabs US filings series: SEC EDGAR financials · LEI ownership · Federal contractors

🎉 Turn SEC enforcement into clean, structured data — no login, no API key, one row per action, with the respondent, action type, date, release and links. Built for compliance, legal and risk-research teams.

🔍 What is the SEC Enforcement Actions — and when should you use it?

Give this actor company or person names, or keywords and it returns matching actions from SEC enforcement and litigation releases (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 SEC action company list for outreach; formation / status monitoring; or a canonical registry record for KYB and due diligence.

Use something else when: you need company firmographics — this is enforcement actions, not a company registry.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/sec-enforcement-actions.

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 SEC action company records using the Apify Actor `foxlabs/sec-enforcement-actions`.
Input: `releaseTypes`, `searchTerm`, `datePreset`, `dateFrom` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"datePreset":"last_30_days","maxResults":100}
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/sec-enforcement-actions.md.

📋 Overview

Everything you need to turn SEC enforcement and litigation releases (official open data) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole feed, one call — name or ID in, matching actions 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~sec-enforcement-actions/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"datePreset":"last_30_days","maxResults":100}'

🚀 Getting Started (3 steps)

1. Choose your targets — company or person names, or keywords.
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

{"datePreset":"last_30_days","maxResults":100}

Field	Type	Description
releaseTypes	array	Which SEC enforcement feeds to pull. Leave empty for all three. Litigation Releases = civil court actions. Administrative Proceedings = SEC in-house orders. AAER…
searchTerm	string	Optional filter matched against the defendant/respondent names and release/file numbers within the selected date range (e.g. a company or person, 'Tesla',…
datePreset	string	Quick filter on the release publication date. Pick 'Custom' to use the From/To fields. Choose 'All time' to crawl the full archive (back to the 1990s).
dateFrom	string	YYYY-MM-DD (e.g. 2026-01-01). Only used when Date range = Custom.
dateTo	string	YYYY-MM-DD. Only used when Date range = Custom. Leave empty for 'today'.
maxResults	integer	Hard cap on dataset rows (across all selected release types). Helps control cost and runtime. Set to 0 for unlimited.
includeFullText	boolean	Fetch each release's detail page and add the full body text, a short summary and linked complaint/order documents. Slower and pricier (one extra request per…
userAgent	string	SEC.gov requires a descriptive User-Agent. A sensible default is used; override only if you have a reason (e.g. include your own contact email).

📤 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
releaseType	Release Type
releaseTypeLabel	Release Type Label
releaseNumber	Release Number
date	Date
dateTime	Date Time
respondents	Respondents
seeAlso	See Also
detailUrl	Detail Url
documentUrls	Document Urls
source	Source

💼 Use cases

1. Compliance screening — check a name against SEC actions. Input: company or person names. Output: actions + dates. Use: a screening result.

2. Risk research — analyse enforcement in a sector. Input: keywords. Output: actions + types. Use: a risk report.

3. Litigation monitoring — track new actions. Input: names, scheduled. Output: new actions. Use: an alert feed.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/sec-enforcement-actions').call({"datePreset":"last_30_days","maxResults":100});
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/sec-enforcement-actions').call(run_input={"datePreset":"last_30_days","maxResults":100})
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 SEC enforcement and litigation releases (official open data).

What do I search by? Company or person names, or keywords.

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

What does each row cover? One SEC enforcement/litigation action: respondent, action type, date, release number and links.

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 SEC enforcement and litigation releases. 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.16 — 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: {"datePreset":"last_30_days","maxResults":100}
• 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

• Dropped empty-promise columns. Removed fileNumber, commentsDue, commentsDueRaw — SEC enforcement and litigation releases (official open data) does not carry them, so they were shipped as always-null columns. Only fields this source actually fills are now emitted.
• 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 SEC enforcement and litigation releases (official open data) by name or registry ID.