Tweet context
/v1/tweets/:id/contextTweet, author, quotes, and retweeters — one call for moderation, research, and AI summaries.
xfetch is a Twitter API alternative for developers: stable read endpoints, workflow-shaped /v1 APIs that return normalized JSON for AI and agent pipelines, and predictable credits for successful calls.
Build X/Twitter data features on /v1 — one call returns the finished shape, ready to drop into RAG, agents, and classifiers.
{
"data": {
"tweet": { "id": "1895…", "like_count": 1240 },
"author": { "username": "jack" },
"quotes": [
{ "username": "naval", "text": "clean JSON" }
],
"retweeters": [
{ "username": "pmarca" },
{ "username": "balajis" }
]
},
"meta": { "credits": { "charged": 3 } }
}Each example shows the final /v1 shape beside the client-side stitching it removes.
Tweet, author, quotes, and retweeters — one call for moderation, research, and AI summaries.
Profile data plus recent_tweets in one response — account intelligence without the second lookup.
Twitter search results plus a single deduped authors array — built for LLM pipelines.
See every /v1 endpoint in the API reference →Basic Reads · Enriched Reads · Workflow APIs
Normalized, deduped JSON that drops into your pipeline — and a machine-readable contract your agents can read on their own.
/v1/search/recent/enriched returns tweets plus a single deduped authors array with normalized fields — ready for embeddings, RAG, classifiers, and summarizers. No scraping glue, no shape drift.
{ "data": { "tweets": [ { "author_id": "12", "text": "shipping /v1 🚀" }, { "author_id": "12", "text": "clean JSON, no glue" }, { "author_id": "44", "text": "drops into RAG" } ], "authors": [ { "id": "12", "username": "jack", "verified": true }, { "id": "44", "username": "naval" } ] } }
Point an agent at the machine-readable contract — it learns the endpoints, parameters, and credit costs on its own.
Single lookups cost 1 credit. Collections start at a base credit plus returned items. Failed calls never touch your balance.
Pick the accounts your product cares about and receive signed tweet.created deliveries when they publish. Read history from the same /v1 API whenever you need it.
Configure eligible account monitors in the dashboard. No monitor API integration required.
xfetch POSTs tweet.created to your webhook destination with a verifiable signature.
Deliveries are signed and retried on failure. The same /v1 reads you already use cover anything in between — no separate replay API to integrate.
tweet.created eventHistory: read past tweets via /v1Credits: deliveries are not meteredx-xfetch-signatureNot metereddeliveries are free/v1 readspreviewPreview included with monthly plans as account monitor slotsSee monitor capacity
/v1 — workflow endpoints like profile lookup, tweet context, and enriched search that return normalized JSON. If you already have official X API read code, /2 keeps a focused 14-endpoint read subset familiar while you migrate — no writes, media, or streaming. Both run on credits with no enterprise contract. See /2 compatibility →tweet.created deliveries when selected accounts publish. Deliveries are retried on failure, and you can read full history any time from the same /v1 endpoints you already use.60 seconds from Google sign-in to your first /v1 response.
No card required. 1,000 credits granted automatically.
One key works across /v1 and /2.
Try /v1/profiles/by-username. Failed calls never charge credits.