# Twitter X Crypto News Scraper (`egsand/twitter-x-crypto-news-scraper`) Actor

- **URL**: https://apify.com/egsand/twitter-x-crypto-news-scraper.md
- **Developed by:** [Enrique G.](https://apify.com/egsand) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Crypto Alpha & Catalyst Detector from X (Twitter) + Instant Alerts 🚀

**Real-time crypto catalyst, news, and alpha detector.** Monitors official project accounts, top exchanges (`@binance`, `@coinbase`), breaking news aggregators, and Tier-1 crypto leaders on X (Twitter). Extracts token listings, exploits, hard forks, airdrops, and token burns, and delivers instant notifications via **Telegram**, **Discord**, or **Custom Webhooks**.

***

### ⚡ Why Use This Actor?

- **Smart Catalyst Classifier (0-100 Impact Score)**: Automatically discards noise, routine chatter, and memes ("GM", "Good vibes"). Only alerts you when a real economic event or catalyst occurs.
- **Categorization & Sentiment Engine**: Identifies whether an event is `EXCHANGE_LISTING`, `HACK_OR_EXPLOIT`, `MAINNET_OR_UPGRADE`, `TOKENOMICS_BURN_UNLOCK`, `AIRDROP`, or `REGULATORY`, tagging it with `BULLISH`, `BEARISH`, or `CRITICAL` sentiment.
- **Entity Extraction**: Automatically extracts coin tickers (`$BTC`, `$SOL`, `$TIA`), smart contract addresses (`0x...`, Solana base58), links, and mentions.
- **Instant Multi-Channel Dispatcher**:
  - 📱 **Telegram Bot**: Sends clean, formatted alerts with emoji severity indicators and direct links.
  - 💬 **Discord Webhook**: Delivers rich color-coded embeds (Green = Bullish, Red = Exploit/Crash alert).
  - 🌐 **Custom Webhooks**: Sends structured JSON payloads directly to your trading bot, n8n/Make automation, or custom dashboard.
- **Schedule & Deduplication Ready**: Enable `onlyNewEvents` to retain state in Apify Key-Value Store so recurring runs (e.g. every 1 or 5 minutes) only alert on newly published catalysts.

***

### 📥 Input Parameters

| Parameter | Type | Default | Description |
| :--- | :--- | :--- | :--- |
| `targetHandles` | Array | `["binance", "coinbase", "Tier10k", "WatcherGuru", "lookonchain", "solana", "arbitrum", "ethereum"]` | List of X (Twitter) usernames without `@` to monitor. |
| `filterTickers` | Array | `[]` (all) | Optional filter for specific coin symbols (e.g. `["BTC", "SOL", "TIA"]`). |
| `categories` | Array | `[]` (all) | Filter by catalyst category: `listing`, `hack`, `mainnet`, `burn`, `partnership`, `airdrop`, `regulatory`. |
| `minImpactScore` | Integer | `30` | Minimum score (0 - 100) to qualify as a catalyst (70+ for high alpha only). |
| `maxEvents` | Integer | `50` | Maximum number of events to output per execution. |
| `maxAgeHours` | Integer | `48` | Maximum post age in hours (ignores older posts). |
| `onlyNewEvents` | Boolean | `false` | When `true`, remembers seen events across scheduled runs and only processes new ones. |
| `telegramBotToken` | Secret String | `""` | Optional Telegram Bot API token for instant chat alerts. |
| `telegramChatId` | String | `""` | Destination Telegram Chat ID or public channel username (e.g. `@mychannel`). |
| `discordWebhookUrl` | Secret String | `""` | Optional Discord Webhook URL for rich channel alerts. |
| `customWebhookUrl` | Secret String | `""` | Optional HTTP POST endpoint URL for your trading bot or backend API. |
| `customWebhookHeaders` | Object | `{}` | Optional headers (e.g. `{"Authorization": "Bearer TOKEN"}`). |
| `proxyConfiguration` | Object | `{}` | Apify Proxy settings (Residential / Datacenter). |

***

### 📤 Output Dataset Format

Every catalyst is saved into the Apify Dataset as a clean, standardized JSON object:

```json
{
  "id": "x-2116926305254133892",
  "source": "x_syndication",
  "handle": "binance",
  "authorName": "Binance",
  "authorVerified": true,
  "tweetUrl": "https://x.com/binance/status/2116926305254133892",
  "publishedAt": "2026-11-01T16:12:16.000Z",
  "ageMinutes": 15,
  "text": "Binance Will List Predict (PREDICT) with Seed Tag Applied...",
  "catalyst": {
    "isCatalyst": true,
    "category": "EXCHANGE_LISTING",
    "sentiment": "BULLISH",
    "urgency": "BREAKING",
    "impactScore": 92,
    "summary": "[EXCHANGE_LISTING] [$PREDICT] @binance: Binance Will List Predict (PREDICT)..."
  },
  "entities": {
    "tickers": ["PREDICT"],
    "contracts": [],
    "urls": ["https://www.binance.com/en/support/announcement/..."],
    "mentions": ["binance"]
  },
  "metrics": {
    "likes": 1577,
    "retweets": 224,
    "replies": 85
  },
  "notificationsSent": {
    "telegram": true,
    "discord": false,
    "customWebhook": true
  },
  "catalystCategory": "EXCHANGE_LISTING",
  "impactScore": 92,
  "sentiment": "BULLISH",
  "tickers": "PREDICT",
  "summary": "[EXCHANGE_LISTING] [$PREDICT] @binance: Binance Will List Predict (PREDICT)..."
}
```

# Actor input Schema

## `targetHandles` (type: `array`):

List of official X accounts (handles without @) to monitor for breaking catalysts and announcements.

## `filterTickers` (type: `array`):

Optional list of coin symbols to filter (e.g. BTC, SOL, ETH, TIA). Leave empty to accept all coins.

## `categories` (type: `array`):

Filter by catalyst types (e.g. listing, hack, mainnet, burn, partnership, airdrop, regulatory). Leave empty to allow all detected catalyst types.

## `minImpactScore` (type: `integer`):

Minimum catalyst importance score required to store and alert (discards general chatter, memes, and routine greetings).

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

Maximum number of events/announcements to output in this run.

## `maxAgeHours` (type: `integer`):

Ignore tweets or news older than this number of hours.

## `onlyNewEvents` (type: `boolean`):

When enabled, stores processed IDs in Apify Key-Value Store so subsequent runs (e.g. cron/schedule) only output and notify unseen catalysts.

## `telegramBotToken` (type: `string`):

Telegram Bot API token to send instant catalyst alerts (e.g. 123456:ABC-DEF...).

## `telegramChatId` (type: `string`):

Target Telegram Chat ID or public channel username (e.g. -100123456789 or @mycryptovip).

## `discordWebhookUrl` (type: `string`):

Discord channel Webhook URL to deliver formatted Rich Embed catalyst alerts.

## `customWebhookUrl` (type: `string`):

HTTP POST endpoint URL to send catalyst JSON payloads to your own backend, trading bot, or n8n workflow.

## `customWebhookHeaders` (type: `object`):

Additional HTTP headers (e.g. Authorization or X-Api-Key) to send with the custom webhook POST.

## `twitterCookies` (type: `array`):

Optional X cookies (such as auth_token and ct0) used when deep browser-based search is required.

## `proxyConfiguration` (type: `object`):

Select Apify residential or datacenter proxies for resilience against rate limits.

## Actor input object example

```json
{
  "targetHandles": [
    "binance",
    "coinbase",
    "Tier10k",
    "WatcherGuru",
    "lookonchain",
    "solana",
    "arbitrum",
    "ethereum"
  ],
  "filterTickers": [],
  "categories": [],
  "minImpactScore": 30,
  "maxEvents": 50,
  "maxAgeHours": 48,
  "onlyNewEvents": false,
  "customWebhookHeaders": {},
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Structured JSON items containing classified crypto catalysts, impact scores (0-100), sentiment, tickers, viral metrics, and original URLs.

# 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("egsand/twitter-x-crypto-news-scraper").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("egsand/twitter-x-crypto-news-scraper").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 egsand/twitter-x-crypto-news-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,egsand/twitter-x-crypto-news-scraper"
        }
    }
}
```

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/1x2tkZ1clLL5ifKIY/builds/zRFHHL3reGW1s0gcF/openapi.json