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.
Try it first — no account. See a profile with recent posts or search results as normalized JSON.
1,000 free creditsHosted MCP for AI agentsFailed calls are not charged
GET/v1/profiles/by-username/elonmusk
ONE REQUEST RETURNS
- Public account details
- Recent posts in the same response
- Normalized JSON for apps and AI
Choose a preset above, then fetch a real response.
Preset demo · your key works with any valid input
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
- TimelinesOriginal posts & reposts, 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 Search API guide Profiles & audience Tweet lookup API 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 — route observed posts where your team works.
When xfetch observes a post from an account you watch, route it to Discord, a generic signed webhook, or both.
Dashboard setup · no polling job
- 01
Pick the accountsany public
@handle— competitors, founders, news - 02
Connect Discordpick a channel, authorize — no webhook URL
- 03
Go liveobserved posts route to the channels you choose
$3/ extra account / month
Watch one account free for 10 days; monthly plans include 2–25 monitor accounts. Deliveries never spend your credits.
MONITORwatch → reactexample
xfetch.ioAPPToday at 4:11 PM
Open on X
Posts xfetch observes, routed to your Discord channel.
Route observed posts to Discord, or use your own signed webhook for custom workflows.See Twitter webhook and 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 posts xfetch observes 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 use the same key and credits. 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?
- Yes — run one real request without an account:
curl https://xfetch.io/api/demoreturns a live profile lookup on a shared demo key. The API reference shows request/response samples per endpoint, /openapi.json is machine-readable, and Google sign-in gets you your own key with 1,000 free credits. - 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 xfetch observes a post from a watched account, it can route a Discord notification card, a generic signed
tweet.createdwebhook, or both. Generic webhooks carryx-xfetch-signature; transient delivery failures retry with bounded backoff. Setup is in the dashboard, with no polling job to run. 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.