# SEC Enforcement Tracker — Litigation, Proceedings & AAER (`foxlabs/sec-enforcement-actions`) Actor

Official SEC.gov enforcement feed: litigation releases, administrative proceedings and accounting & auditing enforcement (AAER). Filter by type, keyword, date. Defendants, release/file numbers, complaint links. Regulatory intel for compliance, securities lawyers, journalists.

- **URL**: https://apify.com/foxlabs/sec-enforcement-actions.md
- **Developed by:** [Berkan Kaplan](https://apify.com/foxlabs) (community)
- **Categories:** Business, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SEC Enforcement Actions ⚖️

🎉 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 queries the source live, so the data is as fresh as the registry itself.

**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: `queries` is a list of company or person names, or keywords. `maxResultsPerQuery` caps rows per query.
Start with: {"queries":["undefined"],"maxResultsPerQuery":50}
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.
- 💰 **Pay only for results** — per-row pricing, empty/failed lookups never billed.
- 🤖 **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

```bash
curl -X POST "https://api.apify.com/v2/acts/foxlabs~sec-enforcement-actions/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["undefined"],"maxResultsPerQuery":50}'
```

### 🚀 Getting Started (3 steps)

1. **Choose your targets** — company or person names, or keywords.
2. **Set the cap** — `maxResultsPerQuery` limits rows per query.
3. **Run and export** — get a clean dataset as JSON, CSV or Excel.

### 📥 Input

```json
{"queries":["undefined"],"maxResultsPerQuery":50}
```

| Field | Type | Description |
|---|---|---|
| `queries` | array | Company or person names, or keywords. |
| `maxResultsPerQuery` | integer | Caps rows per query. |
| `maxConcurrency` | integer | How many queries to fetch at once. |
| `includeRaw` | boolean | Attach the source’s untouched record under `raw`. |

### 📤 Output

One row per company, saved to the dataset. Every row also carries `query`, `scrapedAt`, and — when a lookup fails — an `error` explaining why (never silently dropped, never billed).

| 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**

```javascript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/sec-enforcement-actions').call({"queries":["undefined"],"maxResultsPerQuery":50});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);
```

**Python**

```python
from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/sec-enforcement-actions').call(run_input={"queries":["undefined"],"maxResultsPerQuery":50})
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 `queries` → 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.](https://apify.com/foxlabs/sec-enforcement-actions)

### ❓ 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 `maxResultsPerQuery`, or refine the name.
- **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](https://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](https://apify.com/foxlabs)

### Changelog

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

# Actor input Schema

## `releaseTypes` (type: `array`):

Which SEC enforcement feeds to pull. Leave empty for all three. Litigation Releases = civil court actions. Administrative Proceedings = SEC in-house orders. AAER = accounting & auditing enforcement.

## `searchTerm` (type: `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', 'Coinbase', 'LR-26568'). Case-insensitive substring match. Widen the date range to search further back. Leave empty to list everything.

## `datePreset` (type: `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` (type: `string`):

YYYY-MM-DD (e.g. 2026-01-01). Only used when Date range = Custom.

## `dateTo` (type: `string`):

YYYY-MM-DD. Only used when Date range = Custom. Leave empty for 'today'.

## `maxResults` (type: `integer`):

Hard cap on dataset rows (across all selected release types). Helps control cost and runtime. Set to 0 for unlimited.

## `includeFullText` (type: `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 release). Works for HTML detail pages; PDF-only releases just keep their document link.

## `userAgent` (type: `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).

## Actor input object example

```json
{
  "releaseTypes": [],
  "datePreset": "last_30_days",
  "maxResults": 100,
  "includeFullText": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "releaseTypes": [],
    "datePreset": "last_30_days",
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("foxlabs/sec-enforcement-actions").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "releaseTypes": [],
    "datePreset": "last_30_days",
    "maxResults": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("foxlabs/sec-enforcement-actions").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "releaseTypes": [],
  "datePreset": "last_30_days",
  "maxResults": 100
}' |
apify call foxlabs/sec-enforcement-actions --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,foxlabs/sec-enforcement-actions"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/vPnFSJhnN0PwdVypM/builds/HID9AB6osx6M4AYTD/openapi.json