# SEC Company Monitor (`bb-tradetec/sec-company-monitor`) Actor

Run one explicit, cost-bounded SEC monitoring DAG for an exact company and receive evidence-linked signals plus a verifiable execution receipt.

- **URL**: https://apify.com/bb-tradetec/sec-company-monitor.md
- **Developed by:** [BB](https://apify.com/bb-tradetec) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.20 / 1,000 monitored sec risk signals

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/platform/actors/running/actors-in-store#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 Company Monitor

Give an AI one exact company and a bounded period. Get an explicit SEC
monitoring DAG, evidence-linked signals, and a machine-verifiable execution
receipt.

This is the first outcome-oriented frontdoor above the 36 SEC Suite backend
Actors. It turns `CIK + period + limits` into:

- parallel 8-K event, filing-change, and corporate-action runs;
- optional exact-name enforcement matching;
- deterministic, versioned compatibility projections in a disclosed staging
  Dataset;
- a final disclosure-risk feed;
- one receipt with every Actor, input hash, dependency, charge ceiling,
  run ID, Dataset binding, result count, and coverage gap.

`planOnly` is the default and calls nothing. Its small starter plan uses only
the corporate-actions source and reserves its `0.26 USD` ceiling plus the
`0.51 USD` required by the final risk-feed Actor if you later choose `execute`
(`0.77 USD` total). Add 8-K events or filing changes deliberately; each adds
a `0.50 USD` child-run ceiling. Optional exact-name enforcement adds `0.26
USD`.
`execute` requires `confirmExternalActorCalls: true`. Every paid child run
receives a platform-enforced maximum charge; ceilings are worst-case caps, not
expected or minimum charges.

The workflow makes zero internal LLM calls. `compact` output omits long
evidence bodies while retaining IDs, rules, provenance, and gaps, so an AI can
usually carry less context than with raw filings. Actual token savings depend
on the model, tokenizer, selected evidence, and prompt; no fixed percentage is
claimed.

### Safe plan

```json
{
  "executionMode": "planOnly",
  "requestId": "apple-monitor-plan",
  "company": {"cik": "320193"},
  "periodFrom": "2026-01-01",
  "periodTo": "2026-07-31",
  "sources": ["corporateActions"],
  "maxCorporateActions": 5,
  "maxSignals": 10,
  "outputMode": "compact",
  "maxWorkflowChargeUsd": 0.77
}
```

The Default Dataset contains final `secDisclosureRiskSignal` records.
`EXECUTION_RECEIPT`, `SUMMARY`, and `ERRORS` are stored in the default KVS.

The Actor is implemented, locally tested, and uploaded as a private beta. Its
safe plan-only Cloud run passed; two execute acceptance paths stopped at the
explicit cross-run Dataset boundary and produced no final signal. Selecting
Apify Cloud storage inside A03 did not bypass `LIMITED_PERMISSIONS`: a child
run cannot read the parent run's staging Dataset. The local Monitor now keeps
that Dataset as the disclosed auditable projection and sends the same bounded
records through A03's native inline input contract. A fresh Cloud acceptance
is still required, so the Monitor is not promoted, public, or monetized. See
[`docs/session-handover.md`](./docs/session-handover.md) for the exact build,
run, receipt, and cost evidence.

# Actor input Schema

## `executionMode` (type: `string`):

planOnly returns the exact DAG and budget without calling another Actor. execute runs it.

## `confirmExternalActorCalls` (type: `boolean`):

Must be true in execute mode. Child runs can incur the disclosed charges.

## `requestId` (type: `string`):

Stable caller correlation ID; do not place secrets or personal data here.

## `company` (type: `object`):

Canonical SEC CIK and, only for enforcement matching, the exact legal respondent name.

## `periodFrom` (type: `string`):

Inclusive YYYY-MM-DD source-date lower bound.

## `periodTo` (type: `string`):

Inclusive YYYY-MM-DD source-date upper bound.

## `sources` (type: `array`):

Deterministic source capabilities to call. enforcement additionally requires company.legalName.

## `maxEvents` (type: `integer`):

Hard global cap for the 8-K child Dataset and its result charges.

## `maxComparisons` (type: `integer`):

Hard cap for complete filing-change records and their result charges.

## `maxCorporateActions` (type: `integer`):

Hard cap for corporate-action source records and their result charges.

## `maxEnforcementActions` (type: `integer`):

Hard cap for exact-respondent enforcement records and their result charges.

## `maxSignals` (type: `integer`):

Hard output and result-charge bound for the final feed.

## `outputMode` (type: `string`):

compact suppresses long evidence bodies while retaining identifiers, provenance, rules, and gaps.

## `maxWorkflowChargeUsd` (type: `number`):

Must cover selected paid child-run ceilings: 0.51 for the risk feed, 0.26 for corporate actions or enforcement, plus 0.50 each for 8-K events or filing changes. This is a hard ceiling, not an expected charge.

## `timeoutSecsPerStep` (type: `integer`):

Platform runtime timeout applied independently to every child Actor call.

## Actor input object example

```json
{
  "executionMode": "planOnly",
  "confirmExternalActorCalls": false,
  "requestId": "apple-monitor-plan",
  "company": {
    "cik": "320193"
  },
  "periodFrom": "2026-01-01",
  "periodTo": "2026-07-31",
  "sources": [
    "corporateActions"
  ],
  "maxEvents": 10,
  "maxComparisons": 2,
  "maxCorporateActions": 5,
  "maxEnforcementActions": 10,
  "maxSignals": 10,
  "outputMode": "compact",
  "maxWorkflowChargeUsd": 0.77,
  "timeoutSecsPerStep": 600
}
```

# Actor output Schema

## `signals` (type: `string`):

No description

## `executionReceipt` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `errors` (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 = {
    "executionMode": "planOnly",
    "confirmExternalActorCalls": false,
    "requestId": "apple-monitor-plan",
    "company": {
        "cik": "320193"
    },
    "periodFrom": "2026-01-01",
    "periodTo": "2026-07-31",
    "sources": [
        "corporateActions"
    ],
    "maxCorporateActions": 5,
    "maxEnforcementActions": 10,
    "maxSignals": 10,
    "maxWorkflowChargeUsd": 0.77
};

// Run the Actor and wait for it to finish
const run = await client.actor("bb-tradetec/sec-company-monitor").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 = {
    "executionMode": "planOnly",
    "confirmExternalActorCalls": False,
    "requestId": "apple-monitor-plan",
    "company": { "cik": "320193" },
    "periodFrom": "2026-01-01",
    "periodTo": "2026-07-31",
    "sources": ["corporateActions"],
    "maxCorporateActions": 5,
    "maxEnforcementActions": 10,
    "maxSignals": 10,
    "maxWorkflowChargeUsd": 0.77,
}

# Run the Actor and wait for it to finish
run = client.actor("bb-tradetec/sec-company-monitor").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 '{
  "executionMode": "planOnly",
  "confirmExternalActorCalls": false,
  "requestId": "apple-monitor-plan",
  "company": {
    "cik": "320193"
  },
  "periodFrom": "2026-01-01",
  "periodTo": "2026-07-31",
  "sources": [
    "corporateActions"
  ],
  "maxCorporateActions": 5,
  "maxEnforcementActions": 10,
  "maxSignals": 10,
  "maxWorkflowChargeUsd": 0.77
}' |
apify call bb-tradetec/sec-company-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bb-tradetec/sec-company-monitor"
        }
    }
}

```

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/73PBLAAm2QinAfc4r/builds/XEQBX2vFvIIB8C0Kg/openapi.json