apify-x-research

Apify X Research

Use this skill for public X/Twitter post capture, X Article extraction, profile timeline snapshots, reply-thread extraction, and social-listening datasets.

Actor Choices

• xquik/x-tweet-scraper: default for tweet lookup by ID and keyword/advanced search. Use it first because it is highly rated and cheap pay-per-result.
• scraper_one/x-post-replies-scraper: replies/comments for one or more post URLs. Use postUrls, resultsLimit, and includeOriginalPost.
• fastcrawler/x-twitter-article-to-markdown: provisional default for long-form X Articles when a tweet links to x.com/i/article/.... Use only after confirming the Store metadata is still cheap pay-per-event and recently maintained. It has no review/rating signal, so require a tiny capped smoke test and reject outputs with empty md or mock rows.

Prefer xquik/x-tweet-scraper for original posts and search. For an X URL, extract the numeric /status/<id> value and pass it as tweetIds. Add scraper_one/x-post-replies-scraper only when the task needs replies or audience reaction. For long-form X Articles, first scrape the linking post with xquik/x-tweet-scraper, then pass the linking /status/<id> value, not the /i/article/<id> value, to fastcrawler/x-twitter-article-to-markdown.

Inputs

Single post or profile:

{
  "tweetIds": ["1234567890"],
  "maxItems": 1
}

Search:

{
  "searchTerms": ["from:sama agents"],
  "maxItems": 25,
  "queryType": "Latest"
}

Replies:

{
  "postUrls": ["https://x.com/username/status/1234567890"],
  "resultsLimit": 50,
  "includeOriginalPost": true
}

X Article:

{
  "tweetIds": ["1234567890"]
}

Run Pattern

1. Write input JSON under .tmp/apify-runs/.
2. Run via apify-actor-ops:

bun run ${CLAUDE_PLUGIN_ROOT}/skills/apify-actor-ops/scripts/run_actor.ts \
  --actor xquik/x-tweet-scraper \
  --input .tmp/apify-runs/x-input.json \
  --out .tmp/apify-runs/x-output.json \
  --max-total-charge-usd 0.25 \
  --max-items 25