A developer-direct Twitter/X data API
for read workflows.
xfetch fills the gap between the official X API's enterprise contracts and brittle scrapers — the read workflows developers actually buy API access for, returned as normalized JSON built for AI and agent pipelines, all on one credit-priced contract with no sales call.
Free credits on sign-in
API families, one balance
Core read workflows
Sales calls or contracts
What xfetch is
Two API families on one credit balance, designed from the reads developers actually ship — not from endpoint parity.
The xfetch product layer
Basic Reads, Enriched Reads, and Workflow APIs that collapse multi-call sequences into one named-block response of normalized JSON — built for AI and agent pipelines.
Migration compatibility
Official-style X API read paths and response envelopes, kept as a bounded convenience so existing code can point at xfetch with minimal changes.
Monthly plans also include a preview account-monitor add-on: dashboard-configured monitors deliver signed webhooks when selected eligible accounts post.
What we build — and what we don't
In scope
- Search & social listening
- Profiles, timelines & account intelligence
- Audience & relationship graph
- Tweet context & conversation analysis
- Trends & market research
- AI / agent data pipelines
- Webhook account monitoring (preview)
Out of scope
- A full clone of the official X API
- Writes or automation — posting, liking, following, DMs
- Enterprise procurement — sales calls, MSAs
- A scraper exposing raw upstream payloads
Principles
- 1
Design from workflows
Every endpoint maps to a real customer workflow, not to endpoint parity with the official API.
- 2
Stable, opaque contracts
Stable public contracts and opaque pagination tokens. No upstream provider names or internal implementation details ever leak.
- 3
Predictable credits
You are never charged for failed validation, authentication failures, rate limits, or service-side errors.
- 4
Self-serve from minute one
1,000 free credits on Google sign-in. Mint a key and call the API without talking to anyone.
Contact
Talk to the people building xfetch
Questions, feedback, partnerships, or bug reports — one inbox, read by the team that ships the API. No ticket queue, no tier-one script.