READ API LIVEBuild on /v1 for search, profiles, timelines, audience graph, and tweet context.READ DOCS
WORKFLOW API LIVE

X/Twitter data API for search, profiles, timelines, audience graph, and tweet context

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.

SEE THE API ↗
1,000 free creditsBuilt for AI and agentsFailed calls are not charged
API console
Docs
GET/v1/tweets/1895554281/contextSEND
200 OKsample
JSON
{
  "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 } }
}
opaque pagination tokens · next_token returned when more results are available
FEATURED /V1 API SHAPES · 3 LIVE EXAMPLES

Final JSON, without the stitching.

Each example shows the final /v1 shape beside the client-side stitching it removes.

See every /v1 endpoint in the API reference →Basic Reads · Enriched Reads · Workflow APIs

AI & AGENTS · MACHINE-READABLE

Built for AI apps and agents.

Normalized, deduped JSON that drops into your pipeline — and a machine-readable contract your agents can read on their own.

For your pipelineenriched json

/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.

3 tweets2 authorsdeduped by author_id
See the enriched shape
For your agentcontract

Point an agent at the machine-readable contract — it learns the endpoints, parameters, and credit costs on its own.

PRICING · TRANSPARENT CREDITS

Pay only for what works. No card. No contract.

Single lookups cost 1 credit. Collections start at a base credit plus returned items. Failed calls never touch your balance.

1,000credits, free.
ON GOOGLE SIGN-IN · NO CARD · NEVER EXPIRES
  • $0.150per 1K credits PAYG
  • 61%max savings on monthly plans
  • $0for failed calls — never charged
Example credit costs
/v1/profiles/by-username2 + 5 tweets7cr
/v1/search/recent1 + 20 posts21cr
/v1/users/:id/followers1 + 100 ids / 206cr
See full pricing → every endpoint, every plan
ACCOUNT MONITORING · PREVIEW ADD-ON

Turn watched accounts into signed webhooks.

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.

Preview add-on
  1. 01

    Watch the accounts that matter

    Configure eligible account monitors in the dashboard. No monitor API integration required.

  2. 02

    Receive signed events

    xfetch POSTs tweet.created to your webhook destination with a verifiable signature.

  3. 03

    One API for live and history

    Deliveries are signed and retried on failure. The same /v1 reads you already use cover anything in between — no separate replay API to integrate.

MONITORpreview monitor capacitypreview
Trigger: watched account publishesPayload: signed tweet.created eventHistory: read past tweets via /v1Credits: deliveries are not metered
Starter1 account · 1 webhook
Growth2 accounts · 2 webhooks
Pro5 accounts · 5 webhooks
Scale10 accounts · 10 webhooks
No monitor APIdashboard-configured slotsSigned deliveriesverifiable x-xfetch-signatureNot metereddeliveries are free
signed webhook eventsdashboard-configured slotshistory via /v1 readspreview

Preview included with monthly plans as account monitor slotsSee monitor capacity

COMMON QUESTIONS

Quick answers to what visitors usually wonder.

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, /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 →
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.
What do preview monitor slots include?
Preview monitor slots are included with monthly plans. xfetch POSTs signed 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.
Start path

Ready to make the first X data API call?

60 seconds from Google sign-in to your first /v1 response.

READ THE DOCS
  1. 01

    Sign in with Google

    No card required. 1,000 credits granted automatically.

  2. 02

    Mint your API key

    One key works across /v1 and /2.

  3. 03

    Run a request

    Try /v1/profiles/by-username. Failed calls never charge credits.