Read the post. Let the feed read the image too.
The feed has built-in OCR. After each post, TweetStream sends any text it reads in the images, plus detected tokens and their prices, in a follow-up meta event. TweetStream's median X post detection time was 170 ms over the seven days to September 30, 2026, measured from X's post timestamp to first receipt on a TweetStream server.
Payload shape your bot can inspect
Route by t and op: content envelopes carry author, text, timestamps, and media; meta envelopes carry OCR text plus detected tokens, markets, and prices.
[
{
"v": 1,
"t": "tweet",
"op": "content",
"id": "2064689031777615872",
"ts": 1781095200123,
"d": {
"tweetId": "2064689031777615872",
"kind": "post",
"text": "New token live. CA: 9xQeWvG816bUx9EP...",
"createdAt": 1781095199900,
"receivedAt": 1781095200108,
"author": {
"handle": "@marketdesk",
"name": "Market Account"
},
"media": [
{
"type": "image",
"url": "https://pbs.twimg.com/media/sample-token-chart.jpg"
}
]
}
},
{
"v": 1,
"t": "tweet",
"op": "meta",
"id": "2064689031777615872",
"ts": 1781095200340,
"d": {
"tweetId": "2064689031777615872",
"platform": "twitter",
"ocr": {
"text": "ticker $EDGE, liquidity rising"
},
"detected": {
"tokens": [
{
"symbol": "EDGE",
"contract": "9xQeWvG816bUx9EP...",
"chain": "solana",
"priceUsd": 0.0042,
"sources": ["text", "ocr"]
}
]
}
}
}
]The live speed report measures X post publication to first TweetStream server receipt. Run your consumer near the endpoint for a shorter network path after receipt. Open the live speed report
At X's public pay-per-use rate, 300K Post reads cost about $1,500/mo. Minimum covers 50 monitored accounts for $199/mo. See the X API cost breakdown
What the WebSocket feed includes
Built for the accounts that move crypto and prediction markets: one event stream from first post to enriched signal, without a polling or scraper stack.
- Tweet alerts that catch the state change
- Stream new posts, updates, deletes, pins, and unpins from the accounts in your watchlist, including author fields, media, links, and quote or reply context when available.
- Account profile and follow events
- Use account event envelopes for profile updates, follow notifications, and unfollow notifications instead of building a separate account-monitoring job.
- Built-in OCR for screenshots and charts
- When an attached image contains text, TweetStream can extract it and send the OCR result in a meta envelope. Your bot can inspect that text alongside detected tokens, market references, and live price context.
- A practical WebSocket protocol
- Every message uses the same envelope shape, so bots can route tweet, account, and control events without custom parsing for each feature.
Why teams use TweetStream as a Twitter monitor API
- No polling loop to tune, babysit, or rebuild when traffic spikes
- Published server-detection methodology
- Image OCR and crypto enrichment your team would otherwise build after ingest
- Flat monitored-account limits instead of metered reads for every workflow
Built for the monitored-account workflow
Most crypto teams do not need every public post. They need the small set of accounts that moves price to reach their systems quickly and cleanly.
- Pick the handles.Add the accounts your desk, bot, or Discord channel already watches.
- Open one socket.Authenticate once and receive live JSON envelopes for tweet, account, and control events.
- Route the signal.Send alerts into trading logic, dashboards, Discord, or history replay without maintaining a scraper stack.
Open the WebSocket in minutes
You only need the endpoint and protocols:
WebSocket endpoint: wss://ws-global.tweetstream.io/ws
Protocols: tweetstream.v1, tweetstream.auth.token.YOUR_API_KEY
See the complete WebSocket example for a program you can download and run.
Where this fits
Use TweetStream when speed, payload shape, and enrichment matter more than broad social listening. If you need official write access, compliance archives, or every X API endpoint, use the official X API alongside TweetStream.