User's posts on X (Twitter)
8 tools offer User's posts on X (Twitter), cheapest first. Pick by price, success rate and latency: every one takes a call with one OrcaRouter API key.
Tools, cheapest first
| Tool | Price | Success (7 days) | Median latency | Runs (30 days) | Tier |
|---|---|---|---|---|---|
| X / Twitter User Tweets and RepliesGet up to the requested limit of tweets and replies authored by an X (Twitter) account, with engagement, views, language, and cursor pagination where available. | $0.000495 / call | — | — | 1 | bridged |
| X / Twitter User PostsGet an X (Twitter) account's profile Posts-tab timeline by handle. Results follow profile order: a pinned post may appear first, followed by otherwise reverse-chronological authored posts, reposts, quotes, and self-thread continuations. | $0.000495 / call | — | — | — | bridged |
| X (Twitter) users who reposted by tweet idTwitter: fetch retweet user list (web) | $0.0011 / call | — | — | — | bridged |
| X (Twitter) user's media posts by handleTwitter: fetch user media (web) | $0.0011 / call | — | — | — | bridged |
| X (Twitter) user's replies by handleTwitter: fetch user tweet replies (web) | $0.0011 / call | — | — | — | bridged |
| X (Twitter) user's posts by handle or user idRecent posts of an X (Twitter) user | $0.0011 / call | — | — | — | bridged |
| X (Twitter) user tweets by usernameFetches tweets from a Twitter user's profile by handle. | $0.00207 / credit | — | — | — | bridged |
| X (Twitter) user posts by numeric user idRetrieves posts published by an X (Twitter) user identified by Rest ID, with cursor pagination. | $0.0162 / call | — | — | — | bridged |
Find them from an agent
curl https://api.orcarouter.ai/v1/tools/discover \
-H "Authorization: Bearer $ORCAROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q":"X (Twitter) User'\''s posts"}'Questions
How much does User's posts on X (Twitter) cost?
8 tools offer it, from $0.000495 per call.
How does an agent use these tools?
With one OrcaRouter API key: POST /v1/tools/discover finds them and POST /v1/tools/{id}/run calls one, with the same request shape for every tool here.
