# X / Twitter Fake Followers Check - Are They Real? (`reapx/x-creator-check`) Actor

"They want $4,000 for one post. Is anyone actually seeing it?" Get real engagement rate measured against creators of the same size, follower count, account age and the growth pattern that gives a bought audience away - before the money moves.

- **URL**: https://apify.com/reapx/x-creator-check.md
- **Developed by:** [Tarek Etman](https://apify.com/reapx) (community)
- **Categories:** Social media, Marketing, For creators
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $70.00 / 1,000 x creator profile checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

![reapX - the record of what changed](https://reapx.dev/reapx.gif)

## X Influencer Finder - Build A Shortlist

> "Who actually gets replies in this niche, rather than just having followers?"

Follower counts on X have never been the signal, and no tool ranks by conversation. Filter accounts by topic, follower band and engagement rate, and shortlist the ones people answer.

### ⬇️ Input

Configure target X handles or profile URLs to evaluate conversation depth and audience engagement.

| Field | Type | Description |
|---|---|---|
| `profiles` | Array of strings | Target X handles or profile URLs (for example `nasa`, `nike`, `elonmusk`). |
| `maxItems` | Integer | Safety cap on maximum profiles evaluated. Default: `100`. |

### ⬆️ Output

Each profile item emits a structured JSON record containing computed conversation metrics:

- `replyRate`: Calculated average reply count per post relative to follower size.
- `conversationDepth`: Computed conversation engagement index measuring thread activity and audience replies.
- `screen_name`: X handle string without @ symbol (stable per-row key).
- `name`: Display name of creator.
- `followers_count`: Observed follower count.
- `friends_count`: Number of accounts followed.
- `statuses_count`: Total posts published.
- `rest_id`: Numeric X user REST identifier.
- `description`: Profile bio text.
- `verified`: Boolean verification badge status.
- `scrapedAt`: ISO 8601 timestamp when data was collected.

```json
{
  "replyRate": 12.4,
  "conversationDepth": 8.2,
  "screen_name": "NASA",
  "name": "NASA",
  "followers_count": 92241671,
  "friends_count": 119,
  "statuses_count": 74293,
  "rest_id": "11348282",
  "description": "Making the seemingly impossible, possible.",
  "verified": true,
  "scrapedAt": "2026-08-06T00:00:00.000Z"
}
```

### How it works

1. Connects to native X endpoints over HTTP using guest token authorization.
2. Extracts complete profile metadata, verification badges, and account creation dates.
3. Computes `replyRate` and `conversationDepth` metrics across recent post threads.
4. Emits structured dataset records ready for agency pitch decks and talent shortlists.

### ❓ FAQ

#### Do I need X credentials or cookies?

No login credentials or session cookies are required. Extraction operates on guest token authorization routines.

#### How are conversation depth metrics calculated?

Conversation depth evaluates reply ratios and audience thread participation across recent posts rather than relying on raw follower counts.

### 💬 Your feedback

Need custom X conversation filters or dataset integrations? Contact us at reapxdev@proton.me.

***

reapx · reapx.dev · reapxdev@proton.me

# Actor input Schema

## `profiles` (type: `array`):

X handles, one per line, with or without the @. Paste a shortlist and check them all together.

## `maxItems` (type: `integer`):

How many of the accounts on your list we work through in one run.

## Actor input object example

```json
{
  "profiles": [
    "nasa"
  ],
  "maxItems": 100
}
```

# Actor output Schema

## `items` (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 = {
    "profiles": [
        "nasa"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("reapx/x-creator-check").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 = { "profiles": ["nasa"] }

# Run the Actor and wait for it to finish
run = client.actor("reapx/x-creator-check").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 '{
  "profiles": [
    "nasa"
  ]
}' |
apify call reapx/x-creator-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,reapx/x-creator-check"
        }
    }
}

```

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/aJBn7e4ndUhqhhigC/builds/yNGrJ05Tn4kViWrfV/openapi.json