# Stock Catalyst News Scraper (`seeb/stock-catalyst-radar`) Actor

Scrape public market-news signals and return company names, ticker clues, catalyst summaries, source URLs, timestamps, and opportunity scoring.

- **URL**: https://apify.com/seeb/stock-catalyst-radar.md
- **Developed by:** [Techionik](https://apify.com/seeb) (community)
- **Categories:** News, Automation, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$25.00 / 1,000 catalyst 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/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

## Stock Catalyst Radar

<p align="center"><img src="https://api.apify.com/v2/key-value-stores/dMvcRKFPcfKXiITSx/records/stock-catalyst-radar.svg" alt="Stock Catalyst Radar logo" width="720"></p>

Stock Catalyst Radar turns public ticker symbols into a compact watchlist of recent SEC filing catalysts. It is designed for investors, analysts, newsletter writers, deal researchers, and market-monitoring teams who need clean filing signals without opening every company page manually.

Give the actor one or more tickers such as `AAPL`, `MSFT`, `NVDA`, or `TSLA`. For each matched company, it reads the SEC company submissions feed, extracts recent filings, builds source-backed catalyst rows, and assigns an urgency score based on filing types that commonly matter for market research.

### What It Extracts

Each dataset row represents a real public filing signal and includes:

- `ticker` and `companyName` for the public company
- `catalystType`, such as `8-K`, `10-Q`, `10-K`, `S-1`, `424B`, Form 4, or proxy filings when present
- `filingDate` and `reportDate` from SEC submission metadata
- `accessionNumber` for stable filing identification
- `sourceUrl` pointing directly to the SEC filing document
- `urgencyScore` to help sort shortlists quickly
- `signalSummary` written for fast review
- `scrapedAt` timestamp for exports and scheduled checks

### Typical Uses

- Build a ticker watchlist of recent 8-K and registration filing activity
- Monitor public companies before earnings, investor updates, fundraising, or corporate events
- Feed source-backed filing rows into spreadsheets, dashboards, CRMs, or alerting systems
- Compare filing activity across a small basket of tickers
- Prepare analyst research queues from SEC public data

### Input

- `tickers`: Public ticker symbols to check
- `maxResults`: Maximum rows to return
- `monitorChanges`: Store a snapshot for later scheduled comparisons
- `onlyChanges`: Return only new or changed rows when monitoring is enabled
- `maxRunSeconds`: Runtime guard for predictable scheduled runs
- `requestTimeoutSeconds`: Timeout for each public SEC request

### Output Quality

The actor writes only structured filing rows when it can match the ticker to SEC public company data. If a ticker cannot be matched or public metadata is unavailable, the run stores a notice in the default key-value store instead of adding placeholder dataset rows.

### Notes

This actor uses public SEC metadata. It does not provide financial advice, trading recommendations, or private market data. Always review the linked filing before making decisions.

# Actor input Schema

## `tickers` (type: `array`):

Public stock ticker symbols such as AAPL, MSFT, NVDA, or TSLA.

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

Maximum dataset rows to write.

## `monitorChanges` (type: `boolean`):

Save a snapshot and compare future runs.

## `onlyChanges` (type: `boolean`):

When monitoring is enabled, output only new or changed rows.

## `maxRunSeconds` (type: `integer`):

Hard runtime guard for predictable scheduled runs.

## `requestTimeoutSeconds` (type: `integer`):

Timeout per public HTTP request.

## Actor input object example

```json
{
  "tickers": [
    "AAPL",
    "MSFT"
  ],
  "maxResults": 25,
  "monitorChanges": false,
  "onlyChanges": false,
  "maxRunSeconds": 180,
  "requestTimeoutSeconds": 15
}
```

# Actor output Schema

## `results` (type: `string`):

Open the default dataset to view structured rows, source URLs, scores, and scraped timestamps.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("seeb/stock-catalyst-radar").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("seeb/stock-catalyst-radar").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 '{}' |
apify call seeb/stock-catalyst-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seeb/stock-catalyst-radar"
        }
    }
}

```

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/mBIYJ25iKtSXZSc3Y/builds/jONiEcJJh3AiPw16q/openapi.json