The X/Twitter feed for trading terminals and bots

Xanguard's B2B API is a real-time X (Twitter) feed built for trading terminals, launchpads and trading bots. One WebSocket streams five event types for the accounts you choose: new tweets, deleted tweets, profile changes, new followers, and follows or unfollows. Tweets are detected in a median of ~200 ms, published live and refreshed hourly, and plans start at $49 a month for 50 accounts. If you build a terminal in the mould of Axiom, GMGN, Photon, BullX or Padre, a Telegram trading bot, or a launch tool, this is the X layer you can plug in instead of building and babysitting your own.

Why terminals and bots use a dedicated X feed

• The signal is more than tweets. A developer deleting a contract-address post, a KOL quietly following a new project, a team renaming its account: each is tradable, and each is its own event in the feed.
• Latency you can check. Every tweet event carries created_at, the millisecond post time X embeds in the tweet. Compare it with your own receive time and your logs show our published latency plus your network hop.
• No X developer account, no rate-limit math. You pay by account count, not by read. Compare the costs in Xanguard vs the official X API.
• Your users never see a vendor. Events arrive as JSON for you to render however your product looks.

Latency proof

Measured on production traffic for all paid-plan accounts, from the tweet's own timestamp to first arrival on a Xanguard server. Live 7-day figures at the last site build (05 Oct 2026 16:22 UTC):

Hourly updates, the method and the raw JSON are on the speed page. For how other feeds publish their numbers, see lowest-latency Twitter APIs, measured.

Event types

Also available as separate APIs: X Communities joins, renames and description changes in about 5 seconds (Community Watch, from $100 a month), pump.fun caller callouts and milestones over WebSocket (PumpFun, from $100 a month), and "who called this token" search over the last 24 hours (CA Search, from $100 a month).

Integration in four steps

1. Get a key. Open @B2B_Xanguard_bot, pick a plan and pay in SOL. Your dt_ key is shown once in the confirmation.
2. Add accounts. POST /v1/dt/targets with {"handle": "example_dev"}, or /add in the bot. Up to 1,000 accounts per client.
3. Connect. Open wss://api.xanguard.tech/v1/dt/realtime/ws, wait for HELLO, send LOGIN with your key (and optional filters), then heartbeat every 30 seconds.
4. Render. Handle op: 0 EVENT frames and deduplicate on event_id. Up to 5 connections per key for redundancy or separate services.

const ws = new WebSocket('wss://api.xanguard.tech/v1/dt/realtime/ws');
ws.onmessage = (e) => {
  const m = JSON.parse(e.data);
  if (m.op === 10) ws.send(JSON.stringify({ op: 2, d: { api_key: 'dt_YOUR_KEY', onlyCA: true } }));
  if (m.op === 0) {
    const { event, data } = m.d;          // twitter.post.new, twitter.tweet.deleted, ...
    if (event === 'twitter.post.new') showInFeed(data.author.handle, data.text, data.created_at);
  }
};
setInterval(() => ws.readyState === 1 && ws.send(JSON.stringify({ op: 1 })), 30000);

Login filters: onlyCA (only tweets with a contract address), onlyTicker (only tweets with a $cashtag), types (tweet, retweet, quote, reply, follow, unfollow, follower, deleted and profile changes) and categories. Full protocol: B2B realtime reference and docs. Client code: Node.js and Python.

Switching providers? twitterapi.io stream clients keep their routes and payloads and change the base URL and key (guide). TweetCatcher clients keep the same opcodes (guide).

Pricing

CA Search add-on: 1,000 searches a day $100, 2,000 $180, 5,000 $250. Need more than 1,000 accounts or a custom setup? Ask in @B2B_Xanguard_bot. Prices checked against the live plan list on 5 October 2026; payment is in SOL only.

What to know before you build

• X only. No Truth Social, Instagram or news feeds.
• Real-time by default. Tweets older than 30 seconds are dropped rather than delivered late. Late delivery and a 15-minute replay after reconnect can be switched on per key on request.
• No execution. Xanguard is read-only data. Trading stays in your product.
• No uptime SLA. Past uptime is measured and published on the speed page instead.

Frequently Asked Questions