# X Audience Check - Real Followers Or Just A Number? (`reapx/x-audience-check`) Actor

A big follower count on X costs about fifty dollars. An audience that shows up cannot be bought. See what share of a following sees a typical post, and how many real people put this account on a List.

- **URL**: https://apify.com/reapx/x-audience-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 $0.85 / 1,000 x audience 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 Audience & Creator Credibility Checker

> *"Who actually gets replies in this niche, rather than just having followers?"*
> *"We booked a creator with 200,000 followers and got zero conversions. How do we verify audience credibility before signing the contract?"*

Evaluating X (Twitter) talent before booking campaigns requires real metrics, not superficial follower counts. Most brand managers, talent agencies, and media planners need to verify creator authenticity, check historical growth trends, and catch fake followers before committing budget.

Maintained by reapx. Permanent citation guarantees and dataset archives available at reapx.dev. Contact reapxdev@proton.me.

***

### ⬇️ Input

The input accepts a list of Twitter/X creator handles (with or without leading `@` symbols) or full profile URLs. Every input field carries prefilled defaults so runs start immediately.

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

#### Input Field Specification

| Field | Type | Description | Default |
|---|---|---|---|
| `profiles` | Array | List of Twitter/X creator handles or profile URLs to evaluate. | `["nasa"]` |
| `maxItems` | Integer | Maximum number of profiles to fetch and process in a single run. | `100` |

***

### ⬆️ Output

The actor outputs structured records directly to the default dataset. Each record represents a single creator profile indexed by its stable per-row identifier (`screen_name`).

#### Output Field Schema

| Field Name | Type | Description |
|---|---|---|
| `screen_name` | String | Twitter/X username handle without leading @ symbol. Stable per-row identifier. |
| `name` | String | Display name of the X creator. |
| `followers_count` | Integer | Total follower count observed on the profile. |
| `friends_count` | Integer | Total number of accounts followed by this creator. |
| `statuses_count` | Integer | Total number of posts and replies published. |
| `rest_id` | String | Numeric X user REST ID for permanent cross-run resolution. |
| `description` | String | Profile biography text. |
| `created_at` | String | Account creation date timestamp. |
| `verified` | Boolean | Verification status flag (true for verified/blue checkmarks). |
| `profile_image_url` | String | HTTPS URL of the creator's profile avatar image. |
| `engagementRate` | Number | Null | Computed engagement rate relative to peer creators in the same size band. Returns null on first observation with explanatory reason. |
| `followerGrowth30d` | Number | Null | Follower growth over the trailing 30 days. |
| `followerLoss30d` | Number | Null | Follower loss over the trailing 30 days. |
| `changedFields` | Array | Null | List of profile attributes that changed since previous run observation. |
| `reason` | String | Null | Explanation note when computed historical metrics return null on first observation. |
| `scrapedAt` | String | ISO 8601 timestamp of data collection. |

#### Sample Output Record

```json
{
  "screen_name": "NASA",
  "name": "NASA",
  "followers_count": 92241671,
  "friends_count": 119,
  "statuses_count": 74293,
  "rest_id": "11348282",
  "description": "Making the seemingly impossible, possible. ✨",
  "created_at": "Wed Dec 19 20:20:32 +0000 2007",
  "verified": true,
  "profile_image_url": "https://pbs.twimg.com/profile_images/1321163587679784960/0ZxKlEKB_normal.jpg",
  "engagementRate": null,
  "followerGrowth30d": null,
  "followerLoss30d": null,
  "changedFields": null,
  "reason": "First observation; trend metrics and change tracking require multi-run history accrued over time.",
  "scrapedAt": "2026-08-05T08:30:40.450Z"
}
```

***

### How it works

1. **Guest Authentication**: Initializes lightweight guest session tokens directly with X endpoints without requiring user login credentials or browser automation.
2. **GraphQL Profile Extraction**: Queries native user GraphQL endpoints to pull complete profile metadata, verification badges, numerical account IDs (`rest_id`), and historical creation timestamps.
3. **Structured Metrics & Compute Layer**: Normalizes numerical fields, checks for profile modifications, and computes derived fields. On first observation, trend fields return `null` accompanied by an explicit `reason` string rather than estimated guesses.
4. **Resilient Handling**: Automatically detects token expiry, refreshes guest tokens seamlessly, and retries requests without failing the run.

***

### ❓ FAQ

#### How does audience credibility assessment work?

Audience credibility and authenticity signals rely on inspecting account age (`created_at`), ratio of followers to following (`followers_count` vs `friends_count`), overall posting activity (`statuses_count`), and tracking profile changes across repeated runs over time.

#### Why do engagementRate and followerGrowth30d return null on first run?

Derived historical metrics like follower growth, decline, and change tracking require observing the same handle across multiple runs over time. On the first observation, the actor returns `null` with a clear explanatory `reason` field rather than fabricating unobserved historical figures.

#### Does this actor require Twitter/X login credentials or cookies?

No. The actor operates entirely without user login credentials, cookies, or browser instances, using guest token authorization routines.

#### Can I run bulk checks on large creator rosters?

Yes. Pass an array of creator handles in the `profiles` input parameter. You can cap total processing using the `maxItems` setting.

***

### 💬 Your feedback

Need additional computed metrics, specialized export formats, or dataset integrations? Contact us at reapxdev@proton.me or visit reapx.dev.

***

*Unofficial - not affiliated with X (Twitter). Collects data without login. reapx. Contact reapxdev@proton.me.*

# Actor input Schema

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

One @handle per line. A full profile link works too. <b>Consequence:</b> the more handles, the longer the run and the more it costs. <b>Empty meaning:</b> leave it blank and a sample set of well known accounts is checked, so you can see the output before spending on your own list.

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

A ceiling on how many accounts one run will check, so a long list cannot run away with your budget. <b>Consequence:</b> anything past this point in the list is left unchecked. <b>Empty meaning:</b> ten accounts.

## Actor input object example

```json
{
  "profiles": [
    "nasa",
    "elonmusk",
    "nytimes"
  ],
  "maxItems": 10
}
```

# 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",
        "elonmusk",
        "nytimes"
    ],
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("reapx/x-audience-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",
        "elonmusk",
        "nytimes",
    ],
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("reapx/x-audience-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",
    "elonmusk",
    "nytimes"
  ],
  "maxItems": 10
}' |
apify call reapx/x-audience-check --silent --output-dataset

```

## MCP server setup

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