A tweet with 40,000 likes and one with 4,000 can carry the same real reach, depending on who's behind the numbers. A retweet from an account with 12 followers and a retweet from an account with 400,000 count as the same "+1" in the header stats — but only one of them actually moved the tweet in front of a new audience. Getting past the summary counts means pulling the accounts themselves: who retweeted, who replied, and what reach each of them carries on their own.
If you're an agent (or building one) reading this rather than a human, the full machine-readable schema for every endpoint below lives at mindcase.co/skills.md.
What does the engagement count on a tweet actually break down into?
Pulling a single tweet with Twitter / X Tweets
returns six separate counters: views, likes, retweets, replies,
quotes, and bookmarks. That split matters more than a single
"engagement" total would, because each number means something different —
a like costs a reader nothing and signals almost nothing, a reply means
someone stopped to write a sentence, and a retweet puts the tweet in front
of an entirely different audience than the one that saw it originally.
None of those six fields tell you who's behind them. For that, you need
the accounts, not the counts.
How do you find out who's actually amplifying a tweet?
Three separate pulls cover the three ways a tweet spreads: a retweet puts it in front of a new audience unchanged, a reply adds to the conversation underneath it, and a quote tweet carries it into someone else's own feed with their own commentary attached.
How do you see who retweeted it?
Twitter / X Retweeters takes a tweet URL or numeric tweet ID and returns every account that retweeted it as a full profile — handle, display name, bio, follower and following counts, verification status, location, and links. Suspended or deleted retweeter accounts are skipped automatically, so every row is a real, resolvable account.
curl -X POST "https://api.mindcase.co/v1/data/twitter/retweeters/run?wait=true" \
-H "Authorization: Bearer $MINDCASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"params": {
"tweet_ids": "https://x.com/NASA/status/2039473910987534599",
"max_items_per_tweet": 200
}
}'
# $0.00025 per retweeter profileEach row carries its own followers count, which is the field that turns
a flat retweet count into a reach estimate: 200 retweeters averaging 300
followers each spread a tweet very differently than 200 retweeters
averaging 30,000.
How do you see who replied?
The replies come back richer than the retweeters do.
Twitter / X Replies takes the original tweet as a
conversation root and returns every reply as a full tweet record — full
text, engagement counts on the reply itself, media, quoted content, and
the replier's author profile — with the root tweet included in the same
result set, flagged via isReply so you can tell it apart from the
replies underneath it.
curl -X POST "https://api.mindcase.co/v1/data/twitter/replies/run?wait=true" \
-H "Authorization: Bearer $MINDCASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"params": {
"conversation_id": "https://x.com/NASA/status/2039473910987534599",
"maxResults": 100
}
}'
# $0.00025 per replyReplies age out of Twitter's own search quickly, so this works best pulled soon after a tweet goes up — an old tweet with plenty of historical reply-count in its header can still come back with few or no individual reply rows, because the replies themselves are no longer searchable on X's side.
What about quote tweets?
There's no dedicated "who quoted this" endpoint the way there is for
retweeters and repliers. The practical route is
Twitter / X Tweets again: search using the
original tweet's URL as the query, then keep the rows where isQuote is
true and quotedTweetUrl matches the tweet you're tracking. Every quote
tweet already carries quotedTweetUrl and quotedTweetText as native
fields — you're filtering a broader pull down to the quotes, not
reconstructing anything Twitter itself doesn't expose.
What's the real amplification signal — count, or reach?
The count is what shows up in a tweet's header. The reach is what you get
once you have the accounts behind that count and sum their followers
field — from twitter/retweeters for the retweet side, from each reply
row's author object for the reply side. A tweet retweeted by 40 accounts
with a combined 2 million followers reached a materially different
audience than one retweeted by 400 accounts averaging 50 followers each,
even though the second number looks bigger in the UI. Sorting either list
by follower count also surfaces the specific accounts worth a follow-up —
the ones an outreach or partnerships team would actually want to know
about, not just count.
What can't you get from Mindcase?
Two cases.
No dedicated quote-tweet puller. Retweeters and repliers each have
their own endpoint built for exactly this job. Quote tweets don't — you
get them by filtering a twitter/tweets search, which works, but it's an
extra step the other two don't need.
Native retweets from suspended or deleted accounts are gone. Both
twitter/retweeters and twitter/replies skip accounts that no longer
resolve, which keeps every row usable but also means a count in a tweet's
header can run slightly ahead of what comes back in a pull, if some of
the accounts behind it have since been removed from X.
Which endpoint should you use for which job?
| Endpoint | Input | Price | Best for |
|---|---|---|---|
| Twitter / X Tweets | Handle, tweet URL, or search query | $0.00025 / tweet | Engagement counts, and finding quote tweets via search |
| Twitter / X Retweeters | Tweet URL or tweet ID | $0.00025 / profile | Who retweeted, ranked by their own follower count |
| Twitter / X Replies | Tweet URL or ID as conversation root | $0.00025 / reply | Who replied, with their full profile and reply text |
FAQ
A tweet URL works directly for all three endpoints — Twitter / X Retweeters and Twitter / X Replies also accept the bare numeric tweet ID if you already have it.
Replies age out of Twitter's own search quickly. An older tweet can still show a large reply count in its header while returning few or no individual reply rows, because the replies are no longer searchable on X's side.
No. Both endpoints skip accounts that no longer resolve, so every row returned is a real, currently active account.
No, not directly. Search Twitter / X Tweets using the original tweet's URL as the query, then keep the rows where isQuote is true and quotedTweetUrl matches.
$0.00025 per row across all three endpoints. Pulling 200 retweeters and 100 replies on one tweet costs $0.075 total.
