# Threads Topic Scraper — compare keywords by engagement (`entrogix_works/threads-topic-benchmark`) Actor

Compare several keywords on Meta Threads side by side. One row per topic: median engagement, how concentrated it is, how much is driven by verified accounts, how fresh it is, ranked. Unofficial; not affiliated with Meta.

- **URL**: https://apify.com/entrogix\_works/threads-topic-benchmark.md
- **Developed by:** [Entrogix Works](https://apify.com/entrogix_works) (community)
- **Categories:** Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 topic benchmarkeds

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

## Threads Topic Scraper — compare keywords by engagement

Put several keywords side by side on Meta Threads and get **one row per topic**, ranked by how much engagement a typical post in that conversation actually earns.

Post counts tell you what people are talking about. They do not tell you where a new post has a chance of being seen. A crowded topic where one viral thread absorbs everything is a worse place to enter than a quieter one where reach is spread — and that difference only shows up when you compare topics on the same axes.

### What you get per topic

| Field | Example |
|---|---|
| `engagementRank` | `1` |
| `keyword`, `posts` | `ai agents`, `20` |
| **`medianEngagement`** | `84` |
| `maxEngagement`, `totalEngagement` | `1912`, `3140` |
| **`topShare`** | `0.61` |
| **`verifiedShare`** | `0.15` |
| `medianReplyRatio` | `0.09` |
| `withMediaShare` | `0.4` |
| **`medianAgeHours`** | `6.2` |
| `language`, `languageShare` | `en`, `0.85` |

**`engagementRank`** is ordered by `medianEngagement`, not by total. Total engagement simply rewards whichever topic has more posts, which is not the question — you want to know what a *typical* post earns.

**`topShare`** is the share of all engagement held by the top 10% of posts. Near 1 means a couple of threads own the conversation and a new post is likely to be invisible. Lower means attention is distributed.

**`verifiedShare`** shows how much of the topic is being driven by verified accounts. A topic dominated by large accounts behaves very differently from one where ordinary posts still land.

**`medianReplyRatio`** is replies as a share of all reactions. High values mean people are arguing rather than simply agreeing — useful if you want discussion, and a warning if you do not.

**`medianAgeHours`** is the freshness of the sample. If the typical post is days old, the phrase is not currently moving.

### Summary (key-value store, `TOPIC_SUMMARY`)

`topics`, `topicsWithPosts`, `medianOfMedianEngagement`, `hottest`, and `empty` — the keywords that returned no posts at all.

### Input

```json
{
  "keywords": ["ai agents", "vibe coding", "prompt engineering"]
}
```

**Two or more keywords are required.** One keyword is not a comparison, and the run is rejected rather than returning a single row that answers nothing. If you want the post list for one keyword, use **Threads Search Scraper with engagement metrics** instead.

### Scope and limits — please read

**Threads returns roughly 20 posts per search and this Actor does not scroll.** Every topic is therefore measured on a sample of that size, and raising `samplePerKeyword` will not produce more. That is deliberate: all topics are compared on samples of the same shape, which is what makes the ranking meaningful. It is not an exhaustive count of everything posted about a topic and should not be read as one.

Keywords that return no posts are still returned as a row with `posts: 0` and `engagementRank: null`. They are not silently dropped, so you can tell "nobody is talking about this" apart from "you misspelled it".

This Actor reads public search results only. It does not log in, does not access profiles that require authentication, and does not target private accounts.

**Display names are not returned.** The underlying data carries the `@handle` and whether an account is verified, but not the profile's real-name field — and this Actor's output is aggregate per topic in any case.

### Pricing

Charged **per topic**, not per post — one search covers a whole topic, and the price reflects that.

### Disclaimer

**This is an unofficial tool and is not affiliated with, endorsed by, or sponsored by Meta or Threads.** "Threads" and "Meta" are trademarks of their respective owners and are used here only to describe what this Actor reads. You are responsible for ensuring your use of the collected data complies with applicable law and with Meta's terms.

# Actor input Schema

## `keywords` (type: `array`):

Two or more topics. One keyword is not a comparison and is rejected.

## `serpType` (type: `string`):

Which Threads result set to sample. Recent favours freshness, top favours reach.

## `samplePerKeyword` (type: `integer`):

Threads returns roughly 20 posts per search and this Actor does not scroll, so higher values will not produce a larger sample.

## `minIntervalMs` (type: `integer`):

Pacing between keyword searches.

## `useProxy` (type: `boolean`):

Off by default. Threads is served without a proxy, and residential bandwidth costs about 34x direct.

## `proxyType` (type: `string`):

Only used when the proxy is enabled. Datacenter is far cheaper on bandwidth than residential.

## Actor input object example

```json
{
  "keywords": [
    "ai agents",
    "vibe coding",
    "prompt engineering"
  ],
  "serpType": "default",
  "samplePerKeyword": 25,
  "minIntervalMs": 2000,
  "useProxy": false,
  "proxyType": "DATACENTER"
}
```

# Actor output Schema

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

Every row this run produced, as JSON.

## `summary` (type: `string`):

Totals and medians for this run, so you can judge the rows without reading them all.

# 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 = {
    "keywords": [
        "ai agents",
        "vibe coding",
        "prompt engineering"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("entrogix_works/threads-topic-benchmark").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 = { "keywords": [
        "ai agents",
        "vibe coding",
        "prompt engineering",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("entrogix_works/threads-topic-benchmark").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 '{
  "keywords": [
    "ai agents",
    "vibe coding",
    "prompt engineering"
  ]
}' |
apify call entrogix_works/threads-topic-benchmark --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,entrogix_works/threads-topic-benchmark"
        }
    }
}

```

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/hjKfY2ymSIUOq6RV0/builds/p8H8RApnE3B96TwpI/openapi.json