twitter-api
fetcher-sh/fetcher-skills
Search tweets, resolve profiles, pull timelines and followers—pay-per-call Twitter/X API without developer account or app review.
What is twitter-api?
A drop-in Twitter/X data source for agents offering 15 GET endpoints to search tweets by keyword or advanced operators, resolve profiles by handle, pull timelines and followers, read Lists, and check trends. Use it when you need Twitter/X data without the official API's pricing tiers, app-review process, or OAuth handshake—pay per call in USDC or with prepaid credits.
- Search tweets by keyword, hashtag, or advanced operators (from:, to:, since:, until:, min_faves:, filter:)
- Look up Twitter/X profiles by @handle and fetch extended profile/about information
- Pull a user's tweets, replies, followers, or followings by numeric ID
- Fetch a single tweet by ID, see its replies, and find who retweeted it
- Search for X accounts by name and read Twitter List members or tweets
- Check trending topics by country
How to install twitter-api
npx skills add https://github.com/fetcher-sh/fetcher-skills --skill twitter-api- A fetcher.sh API key (Bearer token starting with bby_live_) from https://fetcher.sh/topup, or ability to pay per call via x402 (USDC on Base, Polygon, Arbitrum, Monad, or Solana)
How to use twitter-api
- 1.Set your API key as an environment variable: export FETCHER_API_KEY="bby_live_xxxxxxxxxxxx" (or omit to pay per call with x402)
- 2.Choose an endpoint based on your need: /api/search for tweets, /api/handle/{handle} for profiles, /api/user/{id}/tweets for timelines, /api/trends for trending topics
- 3.Make a GET request to https://twitter.fetcher.sh with your query parameters (e.g., query=from:OpenAI for tweets from a specific account)
- 4.Parse the JSON response with structure { "status": number, "message": string, "data": ... } — the HTTP status mirrors the status field
- 5.Paginate results using the cursor parameter if needed; use sort=Latest or sort=Top to reorder results
Use cases
- Monitor competitor activity or track hashtags across Twitter/X for sentiment analysis input
- Export follower lists or build data pipelines without official X API rate limits or pricing tiers
- Search tweets from specific accounts or date ranges using X's native advanced search operators
- Resolve Twitter handles to user profiles and pull their timeline or follower data for research
- Track trending topics by country for real-time trend monitoring or news aggregation
- Data analysts and researchers building Twitter/X monitoring pipelines
- Social media managers tracking competitor activity and hashtag trends
- AI agents needing Twitter/X data without OAuth or developer account setup
- Agents performing sentiment analysis or social listening on tweet content
- Anyone needing Twitter/X data without waiting on official API app review
twitter-api FAQ
No. This is a pay-per-call alternative that requires only a fetcher.sh API key or x402 payment; no OAuth, no app review, no waiting on X's official API tiers.
All of X's native operators: from:, to:, since:, until:, min_faves:, min_retweets:, filter:, and -filter: (to exclude). Pass them in the query parameter just as you would on X.
Most endpoints cost $0.005 per call; /api/tweet/{id} costs $0.002. You can prepay credits or pay per call with x402 (USDC on multiple chains).
Yes. Use /api/user/{id}/followers or /api/user/{id}/followings after resolving the handle to a numeric ID via /api/handle/{handle}.
Yes, at https://twitter.fetcher.sh/mcp. Include your Bearer token in the headers, or omit it to pay per call with x402.
Full instructions (SKILL.md)
Source of truth, from fetcher-sh/fetcher-skills.
name: twitter-api description: >- A Twitter API alternative and X API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no OAuth and no developer application. Use when the user wants to search tweets by keyword, hashtag, or advanced operators (from:, to:, since:, until:, min_faves:, filter:), scrape a Twitter/X profile by handle, pull a user's tweets, replies, followers, or followings, fetch a single tweet with its replies or retweeters, read a Twitter List's members or tweets, check trending topics by country, or search for X accounts by name. Also covers Twitter data pipelines, competitor monitoring, hashtag tracking, sentiment analysis input, or follower export without the official X API's pricing tiers or app-review process. keywords:
- x
- twitter-api
- x-api
- twitter-api-alternative
- x-api-alternative
- tweet-search
- social-media
- social-listening
- x402
- ai-agent
Twitter / X API
A drop-in Twitter/X data source for agents: search tweets, resolve profiles, pull timelines and followers, read Lists, and check trends — all as one plain HTTP GET, paid per call. No developer account, no app review, no OAuth handshake, and no waiting on X's own API tiers or rate-limit approvals. If your task mentions a Twitter/X search query, a handle, a tweet ID, or a list ID, this is the skill.
Base URL: https://twitter.fetcher.sh
Also published as x-api — same host, same
endpoints, indexed under the "X" name too since agents and users refer to the
platform both ways.
Quick reference
| Base URL | https://twitter.fetcher.sh |
| Auth | Authorization: Bearer bby_live_... or x402 (USDC) |
| Price | $0.002–$0.005/call |
| Endpoints | 15, all GET |
| MCP | https://twitter.fetcher.sh/mcp |
| Machine-readable | /openapi.json · /llms.txt · /skill.md |
Which endpoint do I need?
| I want to... | Call |
|---|---|
Search tweets by keyword or operator (from:, since:, min_faves:, ...) | GET /api/search |
| Search accounts by name | GET /api/search/users |
| Look up a profile by @handle | GET /api/handle/{handle} |
| Get a user's followers or followings | GET /api/user/{id}/followers or /followings |
| Get a single tweet by ID | GET /api/tweet/{id} |
| See who retweeted a tweet | GET /api/tweet/{id}/retweeters |
| Read a Twitter List's tweets or members | GET /api/list/{id}/tweets or /members |
| Check trending topics for a country | GET /api/trends |
Full param details for every row: references/endpoints.md.
Authentication
Two ways to pay, same data — full mechanics in the fetcher
skill:
# 1. Prepaid credits (recommended — get a key at https://fetcher.sh/topup
# or via POST /api/credits/topup, see the fetcher skill)
export FETCHER_API_KEY="bby_live_xxxxxxxxxxxx"
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/search?query=hello"
# 2. x402 pay-per-call — omit the header; a GET with no payment returns 402
# with machine-readable payment requirements (USDC on Base, Polygon,
# Arbitrum, Monad, or Solana). @x402/fetch signs and retries automatically.
Every response is { "status": number, "message": string, "data": ... }; the
HTTP status mirrors status.
Endpoints (15 — all GET, $0.005/call unless noted)
| Endpoint | Price | What it returns |
|---|---|---|
/api/search | $0.005 | Tweets matching a query; supports X's advanced search operators |
/api/search/users | $0.005 | Accounts matching a name/keyword query |
/api/handle/{handle} | $0.005 | Profile by @handle |
/api/handle/{handle}/about | $0.005 | Extended profile/about info by @handle |
/api/user/{id} | $0.005 | Profile by numeric user ID |
/api/user/{id}/tweets | $0.005 | A user's tweet timeline |
/api/user/{id}/replies | $0.005 | A user's replies |
/api/user/{id}/followers | $0.005 | A user's followers |
/api/user/{id}/followings | $0.005 | Accounts a user follows |
/api/tweet/{id} | $0.002 | A single tweet by ID |
/api/tweet/{id}/replies | $0.005 | Replies to a tweet |
/api/tweet/{id}/retweeters | $0.005 | Accounts that retweeted a tweet |
/api/list/{id}/members | $0.005 | A Twitter List's member accounts |
/api/list/{id}/tweets | $0.005 | A Twitter List's tweet feed |
/api/trends | $0.005 | Trending topics for a country |
{id} / {handle} are path parameters — substitute the real value. Optional
query params (cursor, sort) paginate or reorder; only query (search) and
country (trends) are required elsewhere they appear.
Scenarios
The query on /api/search goes straight to X's own search, so its operators
work as-is: from:, to:, since:, until:, min_faves:, min_retweets:,
filter:, -filter:.
Everything from one account:
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/search?query=from%3AOpenAI&sort=Latest"
Between two dates:
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
--data-urlencode "query=x402 since:2026-01-01 until:2026-02-01" -G \
"https://twitter.fetcher.sh/api/search"
Popular posts only, replies excluded:
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
--data-urlencode "query=ai agents min_faves:500 -filter:replies" -G \
--data-urlencode "sort=Top" \
"https://twitter.fetcher.sh/api/search"
Search accounts by name:
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
--data-urlencode "query=climate scientist" -G \
"https://twitter.fetcher.sh/api/search/users"
Resolve a profile by handle, then pull its bio/about:
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/handle/nasa"
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/handle/nasa/about"
A user's tweets, replies, followers, or followings (by numeric ID from the handle lookup above):
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/user/11348282/tweets"
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/user/11348282/followers"
A single tweet, its replies, and who retweeted it:
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/tweet/1234567890123456789"
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/tweet/1234567890123456789/replies"
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/tweet/1234567890123456789/retweeters"
A Twitter List's members and tweets:
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/list/1234567890/members"
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/list/1234567890/tweets"
Trending topics for a country:
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
"https://twitter.fetcher.sh/api/trends?country=United%20States"
MCP
{
"mcpServers": {
"twitter": {
"url": "https://twitter.fetcher.sh/mcp",
"headers": { "Authorization": "Bearer bby_live_..." }
}
}
}
Free: search_endpoints, describe_endpoint, check_balance. Paid:
fetch_data (any endpoint above), topup_credits, plus the named shortcut
twitter_search. Drop the headers block to pay per call with x402 instead —
see the fetcher skill for the full flow.
Errors
400— missing/invalid parameter (message names it)401— unknown or rotated key402— payment required (x402 challenge) ortopup_required(credits exhausted)404— not a priced path- No rate limits; no refunds on upstream failures (settlement precedes delivery)
Reference
- Deep dives:
references/endpoints.md(every param) ·references/scenarios.md(onecurlper endpoint) ·references/faq.md·references/comparison.md(vs. the official X API and a browser scraper) - Task guides: search tweets · export followers
- Slash command:
/twitter-search - Full agent setup: https://twitter.fetcher.sh/skill.md
- OpenAPI 3.1 contract: https://twitter.fetcher.sh/openapi.json
- Condensed catalog: https://twitter.fetcher.sh/llms.txt
- Payment, credits, and MCP deep dive:
fetcherskill - Site: https://twitter.fetcher.sh
Related skills
More from fetcher-sh/fetcher-skills and the wider catalog.

x-api
Search X posts, profiles, and trends via HTTP—no OAuth, no app review, pay-per-call in USDC or prepaid credits.

x-scraper
Search X posts, profiles, and trends via HTTP—no OAuth, no app review, pay-per-call or prepaid.

yelp
Pay-per-call Yelp business search, details, and reviews via HTTP—no app approval or daily caps.

youtube-api
YouTube search, channel lookup, video details, and trending—pay-per-call via x402 or prepaid credits, no quota limits.

code-connect-components
Connects Figma design components to code components using Code Connect. Use when user says "code connect", "connect this component to code", "connect Figma to code", "map this component", "link component to code", "create code connect mapping", "add code connect", "connect design to code", or wants to establish mappings between Figma designs and code implementations. Requires Figma MCP server connection.

create-design-system-rules
Generate custom design system rules to guide AI agents in consistent Figma-to-code implementation.