Cut the path from source post to risk-checked decision
Keep your strategy focused on decisions. TweetStream delivers selected X posts as structured events, while Pro, Scale, and Ultra Speed include supported Trump and White House Truth Social posts. Your stack stays in control of market data, risk, and execution.
- Start with the 5 accounts and 1 WebSocket included in the trial.
- Run the complete example, then verify how your bot merges content, meta, update, and delete events.
- Measure the complete decision path on the same watchlist and expand only after the signal proves useful.
What TweetStream handles
- Get the source event first
- Send selected posts and account changes into your strategy without building a polling loop.
- Keep the trading context
- Merge token and contract detection, image OCR, live price context, and prediction-market context when available.
- Handle the full event lifecycle
- Process content, meta, update, delete, pin, profile, follow, and unfollow events through one versioned envelope.
Why teams use it
- TweetStream publishes rolling server-detection percentiles for monitored X posts. Test the same watchlist and measure your complete decision path.
- The 3-day trial includes 5 tracked accounts and 1 WebSocket connection.
- Public fixture-backed examples show a prediction-market router and an enrichment consumer without credentials, network calls, or order placement.
- The complete example covers authentication, reconnects, event envelopes, updates, deletes, and local latency measurement.
Questions
What does TweetStream handle inside a trading bot?
TweetStream supplies selected X events over WebSocket, followed by trading enrichment when available. Pro, Scale, and Ultra Speed include supported Donald Trump and White House Truth Social delivery. Your own services still own market data, strategy, risk, orders, and reconciliation.
Can I connect a trading bot directly?
Yes. Generate an API key, connect with the documented v1 WebSocket protocol, and process structured content and account events from your tracked watchlist.
How should a bot handle enrichment, updates, and deletes?
Act on the first content event only when your strategy allows it, then merge later meta events by tweetId. Apply updates and deletes idempotently so stale content cannot keep a candidate live.