# Twitter/X Account Radar (`titan_coder/twitter-x-radar`) Actor

Monitor X/Twitter accounts for NEW tweets — a daily radar, deduplicated across runs. Pay only for genuinely new, dated tweets you have not seen before; baseline, errors and repeats are free. No login, no account risk.

- **URL**: https://apify.com/titan\_coder/twitter-x-radar.md
- **Developed by:** [Radu Furtuna](https://apify.com/titan_coder) (community)
- **Categories:** Social media
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.12 / 1,000 tweet delivereds

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

## Twitter/X Account Radar 🐦

**Know the moment a tracked account posts — without a single risk to a real X account.**

Most X/Twitter scrapers make you re-pay for the same tweets every run, or quietly bill you for empty/error responses. This one remembers what it already showed you and never uses a logged-in account of its own — public timeline only.

### Why growth/research teams use this

- **Never miss a new post from accounts you watch.** Point it at competitors, brands, or influencers on X; every run finds what's genuinely new since the last check.
- **Pay only for what's actually new.** The first run establishes a baseline of the current timeline — completely free. From then on, you're billed once per new tweet, ever, no matter how many times you re-run.
- **No duplicate charges, guaranteed.** Every tweet is tracked with a permanent, durable record — a re-run, a retry, or a crash never bills you twice. Found the same tweet via two different tracked accounts (e.g. a retweet)? Billed once, not twice.
- **Zero account risk.** No login, no cookies, no session of yours or ours — uses the same public, guest-token route your browser uses to view a public profile logged out.

### How it works

1. Give it a list of X `@handles` you want to track and a `monitorId` to name this watch.
2. The first run silently catalogs the current visible timeline of each account — free, no charge, no data written yet.
3. Every run after that fetches the latest tweets and delivers only the ones published after your monitor started tracking that account — with author, text, likes/retweets/replies, and date.
4. A short digest tells you what's new across all your tracked accounts; an optional webhook can push it to Slack, Telegram, or your own system.

### What you pay for

**One event only — `tweet-delivered`.** Billed once per genuinely new tweet: a reliable publish date after your monitor's baseline for that account. Your very first run's entire visible timeline is free. Repeat deliveries of a tweet you've already been billed for — impossible, by design (a permanent record per tweet prevents it, even across different tracked accounts). Errors, blocked attempts, and unreadable data cost nothing.

On the rare occasion the charge itself can't be confirmed after a tweet has already been written to your dataset, we never retry it and never bill you for it later — you keep that row for free rather than risk a duplicate charge.

### What it does NOT promise

Keyword/full-text search across all of X (not just tracked accounts — this specific mode requires a much heavier technical route we haven't built yet), real-time push notifications (this is a scheduled check, not a live feed from X), sentiment analysis, retweets/likes/replies made by *other* users on the tweets we find (only the tracked account's own tweets), a guarantee against X changing or blocking the public route this actor uses at any time (it's not an official API), full coverage of a very high-volume account's entire history in a single baseline pass (see Limits below).

### Input

| Field | What it does |
|---|---|
| `monitorId` | Names this watch's own durable history — required, since the whole point is remembering what you've already seen |
| `handles` (1–30) | X accounts to track, with or without `@` |
| `notifyOn` | `new_tweets` (default) fires the webhook only when something new showed up; `always`/`never` for the rest |
| `webhookUrl` | HTTPS only; delivers the digest of new tweets as JSON |

### Output

- **Dataset** — one row per genuinely new tweet found: author, text, date, engagement counts, and which of your tracked accounts it was found through.
- **Key-value store** — a short digest (per-account counts) and a coverage report showing how many accounts answered cleanly vs. partially vs. failed, with reasons.
- **Run status** — a clear reason on bad input, a busy monitor, or low coverage; anything already saved and billed stays saved and billed. A run that overran its time budget is reported as failed, not silently truncated as a success.

### Limits (v1)

Up to 30 accounts, up to 8 pages of tweets per account per run; one retry per account on a transient error; an early stop if too many accounts fail in a row, so a bad run doesn't burn through your budget for nothing. Your first run for a given account captures a snapshot down to that page limit — older history beyond that snapshot is not retroactively backfilled later. This never affects billing correctness: your billing baseline is fixed at the moment of that first run regardless of how deep the snapshot reached, and a tweet is never charged twice no matter what.

### A note on the source

Data comes from X's public GraphQL endpoints via the same request pattern a logged-out browser makes — no login, no cookies, no account of ours or yours at risk. This is not an official API; X's Terms of Service restrict automated access, and the route itself could change or be blocked at any time — use this at your own discretion.

# Actor input Schema

## `monitorId` (type: `string`):

Name of this monitoring set (a-z, 0-9, dash; up to 40 chars). Keeps its own durable history of already-seen tweets — required, since the whole product is about dedup between runs.

## `handles` (type: `array`):

1-30 X (Twitter) handles, with or without @ (e.g. "apify" or "@apify"). No login needed, no account risk — public timeline only.

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

v1 supports only "x". Kept as a list for schema compatibility with future sources.

## `notifyOn` (type: `string`):

new\_tweets — post the webhook only when new tweets were found; always — post it every run; never — do not call webhookUrl at all.

## `webhookUrl` (type: `string`):

Optional. Receives the digest of new tweets as JSON (POST). HTTPS only; private/loopback addresses are rejected; redirects are not followed.

## Actor input object example

```json
{
  "monitorId": "my-accounts",
  "sources": [
    "x"
  ],
  "notifyOn": "new_tweets"
}
```

# Actor output Schema

# 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 = {
    "monitorId": "my-accounts",
    "sources": [
        "x"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("titan_coder/twitter-x-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 = {
    "monitorId": "my-accounts",
    "sources": ["x"],
}

# Run the Actor and wait for it to finish
run = client.actor("titan_coder/twitter-x-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 '{
  "monitorId": "my-accounts",
  "sources": [
    "x"
  ]
}' |
apify call titan_coder/twitter-x-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,titan_coder/twitter-x-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/hDkSePzsXlLrhDxke/builds/U1UvntQyB8kWL2oEg/openapi.json