Individual posts
Fetch one public post with normalized author, media, metrics, and referenced-post data.
READ-ONLY X DATA, NORMALIZED
Give agents the whole conversation.
Profiles, tweets, timelines, search, and queued exports through a read-only HTTP API.
One requestFull context
Spend on data, not access.
Public X reads at a price that works for products, research, and agents with an appetite for context.
Live reads$0.10per 1,000 posts
Queued reads$0.05per 1,000 posts
Official X API$5.00per 1,000 reads
Up to 50x less for live reads. Up to 100x less for queued jobs.
Get the data around the post.
A post is useful. The account, timeline, media, metrics, and references around it make it actionable.
Complete histories
Move through a public account history without building your own pagination and normalization layer.
Queued exports
Queue a larger search or account timeline and download private gzip NDJSON when it is ready.
Public-post search
Search public X posts with a predictable response shape for apps and agent tools.
Normalized JSON
Users and tweets keep a consistent response shape across every public HTTP route.
TWO REQUEST MODES
Use the interface your stack already speaks.
Call a predictable REST endpoint from any language or runtime.
curl /api/v1/users/marclou/tweets?limit=20 \
-H "Authorization: Bearer $TWITTERXAPI_KEY"curl /api/v1/jobs -X POST \
-H "Authorization: Bearer $TWITTERXAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"operation":"user_tweets","username":"marclou","limit":500}'200 OKapplication/json
{ items: Tweet[], count: number }Context that survives the handoff.
Your agent receives consistent objects instead of raw page fragments, so it can reason across authors, timelines, media, and references.
- FetchRequest a tweet, account, timeline, or search.
- NormalizeReceive one stable, fully typed response shape.
- ActRoute the context into research, monitoring, or your own workflow.
Pay for what you read.
No hidden three-million-post ceiling. Start with five authenticated requests free, then choose live speed or queued economics.
Start freeQuestions, answered plainly.
Read-only public data, clear billing, and no implied relationship with X Corp.
Is TwitterXAPI affiliated with X Corp.?
No. TwitterXAPI is an independent service and is not affiliated with, endorsed by, or sponsored by X Corp.
What can I read?
Public posts, account profiles, account timelines, and public-post search results.
Can the API post or modify data?
No. The service is read-only. It does not publish posts, like content, follow accounts, or modify X data.
How do queued requests work?
Larger search and account-timeline jobs run in the background and produce a private gzip NDJSON download. Queued reads cost $0.05 per 1,000 items.
Is there a monthly post cap?
TwitterXAPI does not impose the hidden three-million-post cap described for the official X API. Normal account and service limits still apply.
FIVE REQUESTS ARE ON US