Connection check
verified live · 26h ago
socialdata
Twitter (X) API alternative for AI agents: tweet search, profiles, followers. $0.0002 per result.
Tools
14
GitHub stars
—
Installs / wk
—
Licence
—
Transport
streamable-http
Last checked
26h ago
Tools & capabilities
14 toolsRead from the running server on 26h ago.
check_is_following
read-only
source_user_id*target_user_id*
Check whether one Twitter/X user follows another. Far cheaper than fetching a follower list — use this whenever the question is about a specific pair of accounts. Both IDs must be… Check whether one Twitter/X user follows another. Far cheaper than fetching a follower list — use this whenever the question is about a specific pair of accounts. Both IDs must be numeric.
get_list_tweets
read-only
cursorlist_id*
Fetch one page of posts from a Twitter/X list, newest first. A page is large — around 100 posts — plus a next_cursor. Billing is per result, so one call here costs several times a… Fetch one page of posts from a Twitter/X list, newest first. A page is large — around 100 posts — plus a next_cursor. Billing is per result, so one call here costs several times a single-user timeline call; do not page through a busy list unless the user asked for that.
get_tweet
read-only
tweet_id*
Fetch a single Twitter/X post by its numeric ID, including engagement counts. Bills one post request against the caller's balance. Fetch a single Twitter/X post by its numeric ID, including engagement counts. Bills one post request against the caller's balance.
get_tweet_comments
read-only
cursortweet_id*
Fetch one page of replies to a Twitter/X post. Returns about 20 replies plus a next_cursor. The first item of a page can repeat the last item of the previous page, so de-duplicate… Fetch one page of replies to a Twitter/X post. Returns about 20 replies plus a next_cursor. The first item of a page can repeat the last item of the previous page, so de-duplicate by post id when paging. Each call bills against the caller's balance — do not page through the whole conversation unless the user asked for that.
get_tweet_thread
read-only
cursortweet_id*
Fetch one page of a Twitter/X thread — the chain of follow-up posts the author wrote under their own post ("1/", "2/", ...). Give it the ID of any post in the chain and it returns… Fetch one page of a Twitter/X thread — the chain of follow-up posts the author wrote under their own post ("1/", "2/", ...). Give it the ID of any post in the chain and it returns that chain in order. It does NOT return what other people replied; use get_tweet_comments for those. A post the author never followed up on is a one-post thread and correctly returns just that post. Roughly 30 posts per page plus a next_cursor, so a long thread takes several calls. Each call bills against the caller's balance — do not page through a long thread unless the user asked for that.
get_user_by_id
read-only
user_id*
Look up a Twitter/X user profile by numeric user ID. Bills one user request against the caller's balance. Look up a Twitter/X user profile by numeric user ID. Bills one user request against the caller's balance.
get_user_by_username
read-only
username*
Look up a Twitter/X user profile by username (handle). Returns the profile including follower and following counts. Bills one user request against the caller's balance. Look up a Twitter/X user profile by username (handle). Returns the profile including follower and following counts. Bills one user request against the caller's balance.
get_user_followers
read-only
cursoruser_id*
Fetch one page of a user's followers. This is one of the most expensive tools: a page is set upstream and can run to ~100 user records, every one of which is billed. Never page thr… Fetch one page of a user's followers. This is one of the most expensive tools: a page is set upstream and can run to ~100 user records, every one of which is billed. Never page through a large account's followers without the user explicitly asking. Requires a numeric user ID.
get_user_following
read-only
cursoruser_id*
Fetch one page of the accounts a user follows. Expensive: a page is set upstream and can run to ~100 user records, every one of which is billed. Never page through a large account'… Fetch one page of the accounts a user follows. Expensive: a page is set upstream and can run to ~100 user records, every one of which is billed. Never page through a large account's following list without the user explicitly asking. Requires a numeric user ID.
get_user_mentions
read-only
cursorusername*
Fetch one page of posts mentioning a given user, newest first. Returns about 20 posts plus a next_cursor. The first item of a page can repeat the last item of the previous page, so… Fetch one page of posts mentioning a given user, newest first. Returns about 20 posts plus a next_cursor. The first item of a page can repeat the last item of the previous page, so de-duplicate by post id when paging. Each call bills against the caller's balance.
get_user_tweets
read-only
cursoruser_id*
Fetch one page of a user's own posts (excluding replies), newest first. Returns about 20 posts plus a next_cursor. If the account has a pinned post it is prepended to every page, s… Fetch one page of a user's own posts (excluding replies), newest first. Returns about 20 posts plus a next_cursor. If the account has a pinned post it is prepended to every page, so de-duplicate by post id when paging. Each call bills against the caller's balance — do not page through a whole timeline unless the user asked for that. Requires a numeric user ID: call get_user_by_username first if you only have a handle.
get_user_tweets_and_replies
read-only
cursoruser_id*
Fetch one page of a user's posts including their replies, newest first. Returns about 20 items plus a next_cursor. If the account has a pinned post it is prepended to every page, s… Fetch one page of a user's posts including their replies, newest first. Returns about 20 items plus a next_cursor. If the account has a pinned post it is prepended to every page, so de-duplicate by post id when paging. Each call bills against the caller's balance. Requires a numeric user ID: call get_user_by_username first if you only have a handle.
search_tweets
read-only
typequery*cursor
Search Twitter/X posts. Returns one page of about 20 results plus a next_cursor, and bills one search request against the caller's balance. The query supports Twitter's advanced s… Search Twitter/X posts. Returns one page of about 20 results plus a next_cursor, and bills one search request against the caller's balance. The query supports Twitter's advanced search operators, and using them is almost always better than a bare keyword search: from:handle posts by an account to:handle replies to an account @handle posts mentioning an account #tag hashtag "exact phrase" phrase match since:2026-01-01 posts on or after a date until:2026-02-01 posts before a date min_faves:100 at least N likes min_retweets:10 at least N retweets filter:links posts containing links -filter:replies exclude replies Combine them freely: from:jack min_faves:500 since:2026-01-01
search_users
read-only
query*