Back to Details

twitter-api

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Twitter / X API

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.
这是面向Agent的即插即用型Twitter/X数据源：搜索推文、解析个人主页、获取时间线和关注者、查看列表、查询热门话题——所有操作均通过简单的HTTP GET请求完成，按调用付费。无需开发者账号、无需应用审核、无需OAuth握手，也无需等待X官方API的层级限制或速率限制审批。如果你的任务涉及Twitter/X搜索查询、用户名、推文ID或列表ID，那么这个Skill就适合你。
Base URL: 
https://twitter.fetcher.sh
该服务也以
x-api
为名发布——同一主机、同一端点，同时以"X"名称索引，因为Agent和用户对该平台的称呼两种都有。

Quick reference

快速参考

Base URL
https://twitter.fetcher.sh
Auth
Authorization: Bearer bby_live_...
or x402 (USDC)
Price$0.002–$0.005/call
Endpoints15, all 
GET
MCP
https://twitter.fetcher.sh/mcp
Machine-readable
/openapi.json
· 
/llms.txt
· 
/skill.md
Base URL
https://twitter.fetcher.sh
认证方式
Authorization: Bearer bby_live_...
或 x402（USDC）
价格$0.002–$0.005/次调用
端点数量15个，均为
GET
请求
MCP
https://twitter.fetcher.sh/mcp
机器可读资源
/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
.
我想要...调用端点
按关键词或运算符（
from:
、
since:
、
min_faves:
等）搜索推文
GET /api/search
按名称搜索账号
GET /api/search/users
通过@用户名查询个人主页
GET /api/handle/{handle}
获取用户的关注者或关注列表
GET /api/user/{id}/followers
或 
/followings
通过ID获取单条推文
GET /api/tweet/{id}
查看谁转发了某条推文
GET /api/tweet/{id}/retweeters
查看Twitter列表的推文或成员
GET /api/list/{id}/tweets
或 
/members
查询某国的热门话题
GET /api/trends
每一行的完整参数详情：
references/endpoints.md
。

Authentication

认证方式

Two ways to pay, same data — full mechanics in the 
fetcher
skill:
bash
undefined
两种付费方式，获取的数据一致——完整机制见
fetcher
Skill：
bash
undefined

1. Prepaid credits (recommended — get a key at https://fetcher.sh/topup

1. 预付费（推荐——在https://fetcher.sh/topup获取密钥

or via POST /api/credits/topup, see the fetcher skill)

或通过POST /api/credits/topup，详见fetcher skill）

export FETCHER_API_KEY="bby_live_xxxxxxxxxxxx" curl -H "Authorization: Bearer $FETCHER_API_KEY"
"https://twitter.fetcher.sh/api/search?query=hello"
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

2. x402按调用付费——省略请求头；无付费信息的GET请求会返回402

with machine-readable payment requirements (USDC on Base, Polygon,

包含机器可读的付费要求（在Base、Polygon、Arbitrum、Monad或Solana链上使用USDC支付）。@x402/fetch会自动签名并重试请求。

Arbitrum, Monad, or Solana). @x402/fetch signs and retries automatically.

—

Every response is `{ "status": number, "message": string, "data": ... }`; the
HTTP status mirrors `status`.

所有响应格式均为`{ "status": number, "message": string, "data": ... }`；HTTP状态码与`status`字段一致。

Endpoints (15 — all GET, $0.005/call unless noted)

端点列表（15个——均为GET请求，除非特别说明，价格为$0.005/次调用）

EndpointPriceWhat it returns
/api/search
$0.005Tweets matching a query; supports X's advanced search operators
/api/search/users
$0.005Accounts matching a name/keyword query
/api/handle/{handle}
$0.005Profile by @handle
/api/handle/{handle}/about
$0.005Extended profile/about info by @handle
/api/user/{id}
$0.005Profile by numeric user ID
/api/user/{id}/tweets
$0.005A user's tweet timeline
/api/user/{id}/replies
$0.005A user's replies
/api/user/{id}/followers
$0.005A user's followers
/api/user/{id}/followings
$0.005Accounts a user follows
/api/tweet/{id}
$0.002A single tweet by ID
/api/tweet/{id}/replies
$0.005Replies to a tweet
/api/tweet/{id}/retweeters
$0.005Accounts that retweeted a tweet
/api/list/{id}/members
$0.005A Twitter List's member accounts
/api/list/{id}/tweets
$0.005A Twitter List's tweet feed
/api/trends
$0.005Trending 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.
端点价格返回内容
/api/search
$0.005匹配查询条件的推文；支持X的高级搜索运算符
/api/search/users
$0.005匹配名称/关键词查询的账号
/api/handle/{handle}
$0.005通过@用户名获取的个人主页信息
/api/handle/{handle}/about
$0.005通过@用户名获取的扩展个人主页/简介信息
/api/user/{id}
$0.005通过数字用户ID获取的个人主页信息
/api/user/{id}/tweets
$0.005用户的推文时间线
/api/user/{id}/replies
$0.005用户的回复内容
/api/user/{id}/followers
$0.005用户的关注者列表
/api/user/{id}/followings
$0.005用户关注的账号列表
/api/tweet/{id}
$0.002通过ID获取的单条推文
/api/tweet/{id}/replies
$0.005某条推文的回复内容
/api/tweet/{id}/retweeters
$0.005转发某条推文的账号列表
/api/list/{id}/members
$0.005Twitter列表的成员账号
/api/list/{id}/tweets
$0.005Twitter列表的推文信息流
/api/trends
$0.005某国的热门话题
{id}
/ 
{handle}
为路径参数——请替换为实际值。可选查询参数（
cursor
、
sort
）用于分页或重新排序；仅
query
（搜索）和
country
（热门话题）为对应场景下的必填参数。

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:
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://twitter.fetcher.sh/api/search?query=from%3AOpenAI&sort=Latest"
Between two dates:
bash
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:
bash
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:
bash
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:
bash
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):
bash
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:
bash
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:
bash
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:
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://twitter.fetcher.sh/api/trends?country=United%20States"
/api/search
的查询语句直接对接X的原生搜索，因此其运算符可直接使用：
from:
、
to:
、
since:
、
until:
、
min_faves:
、
min_retweets:
、
filter:
、
-filter:
。
获取某一账号的所有内容：
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://twitter.fetcher.sh/api/search?query=from%3AOpenAI&sort=Latest"
获取指定日期范围内的内容：
bash
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"
仅获取热门帖子，排除回复：
bash
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"
按名称搜索账号：
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  --data-urlencode "query=climate scientist" -G \
  "https://twitter.fetcher.sh/api/search/users"
通过用户名解析个人主页，然后获取其简介信息：
bash
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"
获取用户的推文、回复、关注者或关注列表（使用上述用户名查询得到的数字ID）：
bash
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"
获取单条推文、其回复以及转发者：
bash
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"
获取Twitter列表的成员和推文：
bash
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"
查询某国的热门话题：
bash
curl -H "Authorization: Bearer $FETCHER_API_KEY" \
  "https://twitter.fetcher.sh/api/trends?country=United%20States"

MCP

MCP配置

json
{
  "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.
json
{
  "mcpServers": {
    "twitter": {
      "url": "https://twitter.fetcher.sh/mcp",
      "headers": { "Authorization": "Bearer bby_live_..." }
    }
  }
}
免费接口：
search_endpoints
、
describe_endpoint
、
check_balance
。付费接口：
fetch_data
（上述任意端点）、
topup_credits
，以及快捷方式
twitter_search
。若使用x402按调用付费，可移除
headers
块——完整流程见
fetcher
Skill。

Errors

错误说明

  • 400
    — missing/invalid parameter (message names it)
  • 401
    — unknown or rotated key
  • 402
    — payment required (x402 challenge) or 
    topup_required
    (credits exhausted)
  • 404
    — not a priced path
  • No rate limits; no refunds on upstream failures (settlement precedes delivery)
  • 400
    —— 参数缺失/无效（错误信息会指明具体参数）
  • 401
    —— 密钥未知或已过期
  • 402
    —— 需要付费（x402验证）或
    topup_required
    （余额耗尽）
  • 404
    —— 路径未定价
  • 无速率限制；上游服务故障时不予退款（结算先于数据交付）

Reference

参考资源