LIVE · 31 READ ENDPOINTS
Twitter data API for search, profiles, timelines, audience graph, and tweet context
xfetch gives people and agents current X/Twitter public data: stable REST endpoints and hosted MCP tools that return normalized JSON for search, analysis, and AI pipelines.
1,000 free creditsHosted MCP for AI agentsFailed calls are not charged
GET/v1/profiles/by-username/elonmusk200 OK
{
"data": {
"user": {
"username": "elonmusk",
"name": "Elon Musk",
"verified": true,
"follower_count": 240158775,
"following_count": 1352,
"tweet_count": 103804,
"created_at": "2009-06-02T20:12:29.000Z"
},
"recent_tweets": [
{ "id": "2063073142306750576", "like_count": 56743,
"text": "Starlink connecting schools in Bolivia" },
{ "id": "2063145931554406899", "like_count": 6138,
"text": "Join our AI recommendations & advertising…" }
]
},
"meta": {
"credits": { "charged": 3, "remaining": 997 }
}
}normalized JSON · one call returns the profile and recent tweets
CONNECT · REST + MCP
Twitter API over REST — or a hosted MCP server for your agent.
One curl call in, or a question to your agent — the same normalized data, either way.
two ways in · one APIsame posts, either way
REST
curl 'https://api.xfetch.io/v1/search/recent?query=$BTC' -H "Authorization: Bearer $XFETCH_API_KEY"call /v1 from any stack — plain HTTPSAGENT
“What are people saying about $BTC right now?” calls search_x_posts({ query: "$BTC" })connect your agent over MCP · Set up MCP →- SearchRecent posts; /enriched dedups authorsrest /v1/search/recentmcp search_x_posts
- Profiles & usersProfile + recent posts, or one lookuprest /v1/profiles/by-username/:usernamemcp lookup_x_profile
- TimelinesPosts, replies & media, paginatedrest /v1/users/:id/tweetsmcp get_x_user_timeline
- Audience graphFollowers/following — ids or profilesrest /v1/users/:id/followersmcp get_x_followers · get_x_following
- Tweet contextAuthor, quotes & retweetersrest /v1/tweets/:id/contextmcp get_x_tweet_context
- Lists, communities & trendsCommunity/list timelines + trendsrest /v1/communities/:id/tweets
All 31 /v1 endpoints AI agent pipelines ContractPoint an agent at the machine-readable contract: /openapi.json · /llms.txt · /llms-full.txt.
- Normalized JSON
- Opaque pagination tokens
- Credit usage on successful REST and MCP results
ACCOUNT MONITORING · READ → REACT
Twitter account monitoring — react the moment an account posts.
When an account you watch posts, the new tweet lands in your Discord in real time.
No code · ready in a few clicks
- 01
Pick the accountsany public
@handle— competitors, founders, news - 02
Connect Discordpick a channel, authorize — no webhook URL
- 03
Go liveset it once — new posts push in real time
$3/ extra account / month
Watch one account free for 10 days; monthly plans include 2–25 monitor accounts. Deliveries never spend your credits.
MONITORwatch → reactlive
xfetch.ioAPPToday at 4:11 PM
Open on X
Every new post, in your Discord the moment it’s posted.
Real-time delivery to Discord, or your own signed webhook for custom workflows.See account monitor details
API PRICING · CREDITS
Predictable API credits — pay only for successful reads.
Single lookups cost 1 credit. Collection, graph, batch, and workflow costs are published by stable pricing key.
1,000credits, free.
ON GOOGLE SIGN-IN · NO CARD · NEVER EXPIRES
≈ 166 profile lookups · 47 searches · 1,000 tweet lookups
- $0.150per 1K credits PAYG
- $19/momonthly plans from
- $0for failed calls — never charged
Example credit costs
/v1/profiles/by-username1 + 5 tweets6cr≈ $0.0009
/v1/search/recent1 + 20 posts21cr≈ $0.003
/v1/users/:id/followers1 + 100 ids / 503cr≈ $0.0004
See full pricing — every endpoint, every plan COMMON QUESTIONS
Twitter data API questions, answered.
- What is xfetch?
- xfetch is a self-serve product for current public X/Twitter data and account monitoring. Read search, profiles, timelines, audience graph, and tweet context as normalized JSON over REST or hosted MCP, or send every new post from watched accounts to Discord and generic signed webhooks. API reads use credits; account monitors are priced per account.
- What is a Twitter data API?
- A Twitter data API gives apps and AI pipelines structured access to public X/Twitter data such as search results, profiles, timelines, audience graph, and tweet context. xfetch returns normalized JSON through
/v1, with focused/2read compatibility and predictable credits for successful calls. - Is this scraping?
- No. xfetch is a stable HTTP read API with normalized response shapes and provider-neutral contracts. Your code targets xfetch endpoints, not raw HTML pages, and the public contract doesn't shift under you.
- Is xfetch a Twitter API alternative?
- Yes. Build on
/v1— workflow endpoints like profile lookup, tweet context, and enriched search that return normalized JSON. If you already have official X API read code,/2keeps a focused 14-endpoint read subset familiar while you migrate. Both run on credits with no enterprise contract. See the Twitter API alternative comparison → See /2 compatibility → - Is the data live?
- Yes. Each request reads current X/Twitter source data at request time and returns xfetch's normalized public response shapes. Public errors use stable codes, and service-side failures are not charged.
- What if my volume grows beyond the published plans?
- Monthly plans go up to Scale at $349/mo for 6 million credits and 2,400 req/min (~40 QPS). For anything bigger, get in touch at hello@xfetch.io.
- Can I evaluate before signing up?
- The API reference shows live request/response samples per endpoint. /openapi.json is machine-readable. Sign in with Google to run real requests against your own API key in the dashboard playground.
- Can my agent use xfetch over MCP?
- Yes. xfetch runs a hosted remote MCP server at
https://api.xfetch.io/mcp. Point any remote-MCP-compatible client at it with your API key as a Bearer token to get six read-only tools — search, profile lookup, tweet context, user timeline, followers, and following. MCP tools spend your normal credits, failed calls aren't charged, and/openapi.jsonstays the API contract. See the MCP setup → For pipeline patterns, see Twitter data API for AI agents. - How do account monitors work?
- When a watched account posts, xfetch pushes the new tweet to Discord or a generic signed webhook in real time. Generic webhooks carry
x-xfetch-signature; failed deliveries retry with bounded backoff. Setup is in the dashboard, no code. Free and PAYG include one 10-day trial monitor slot; monthly plans include monitor accounts (Starter 2, Growth 5, Pro 10, Scale 25). The extra-account rate is $3 per account / month. Deliveries aren't credit-metered.