Xanguard speaks twitterapi.io's API — same routes, same payloads. Point your base URL at us, swap your key, and you're done. You get ~200 ms median detection (published live), the quote-tweets and retweets their monitor drops, and zero footprint on the accounts you track.
The drop-in is the easy part — here's what you actually gain.
Median tweet detection is ~200 ms on paid plans, published live on our speed page. In our own testing, twitterapi.io's user monitor took about 10 seconds to surface a tweet (twitterapi.io states a median under 500 ms for its stream).
In our testing, twitterapi.io's monitor silently dropped quote-tweets and retweets — often the actual signal. Xanguard delivers every type: posts, replies, quotes, retweets.
Xanguard never follows the accounts you monitor or adds them to lists. The accounts you track are never notified that someone's watching.
Your routes, request bodies, and tweet parser stay exactly the same.
1Get your Xanguard key from @B2B_Xanguard_bot — it starts with dt_.
2Repoint your REST calls. Same paths, same bodies — only the host changes:
X-API-Key header stays — just use your new dt_ key.3Repoint the realtime WebSocket. Same header, same payload shape:
x-api-key header. Tweets arrive as {"event_type":"tweet","tweets":[…]} — your existing parser works unchanged.| Action | twitterapi.io | Xanguard |
|---|---|---|
| Add a handle | POST /oapi/x_user_stream/add_user_to_monitor_tweet | identical path |
| Remove a handle | POST /oapi/x_user_stream/remove_user_to_monitor_tweet | identical path |
| List handles | GET /oapi/x_user_stream/get_user_to_monitor_tweet | identical path |
| Realtime tweets | wss://ws.twitterapi.io/twitter/tweet/websocket | wss://api.xanguard.tech/twitter/tweet/websocket |
| Auth | X-API-Key header | same header, dt_ key |
Request bodies and tweet event shapes match twitterapi.io's — no code changes beyond the host and the key.
twitterapi.io figures are from our own testing of their user-monitor stream (checked September 2026). Xanguard latency is published live at /speed/.
| twitterapi.io monitor | Xanguard | |
|---|---|---|
| Tweet delivery latency | ~10s in our testing (they state a median under 500 ms) | ~200 ms median |
| Quote-tweets & retweets | dropped | delivered |
| Footprint on tracked accounts | may follow / list them | none — invisible |
| Migration effort | — | change base URL + key |
| Beyond tweets | tweets only | + profile changes, new-follower, deleted-tweet |
Grab a key, change two strings, ship. Pay in SOL.
Still comparing? See twitterapi.io alternatives compared (prices and published latency, checked 5 October 2026).