# Xanguard — Real-Time Twitter/X Monitoring Platform (Full Reference) > Xanguard is a real-time Twitter/X monitoring platform that delivers sub-second tweet alerts, community gate detection, profile watching, follow/unfollow tracking, and engagement monitoring across 9 products. Xanguard serves crypto traders, DeFi protocols, trading bots, and AI agents through Telegram bots, WebSocket feeds, REST APIs, and HMAC-signed webhooks. The B2B WebSocket API uses TweetCatcher-compatible opcodes and starts at $49/mo for 50 handles. - Website: https://xanguard.tech - API Documentation: https://docs.xanguard.tech - OpenAPI Spec: https://xanguard.tech/openapi.json - Health: GET https://xanguard.tech/health - Blog: https://xanguard.tech/blog/ --- ## Core Products ### 1. Tweet Alerts (@Xanguard_bot) — Free + Paid ($19-$349/mo) Sub-second tweet notifications via push-based detection infrastructure. Delivery channels include Telegram, REST API, WebSocket, and HMAC-SHA256 signed webhooks. Features keyword filtering, contract address extraction, reply/quote filtering, and mute controls. The free tier supports 1 handle with Telegram delivery. Paid tiers support 10 to 500 handles with full API and webhook access. - Bot: https://t.me/Xanguard_bot - Page: https://xanguard.tech/ ### 2. Community Watch (@F_xanguard_bot) — $100-$1,500/mo Real-time Twitter community gate monitoring with approximately 5-second detection. Tracks community joins, creates, renames, description changes, follows, and new follower events. - Bot: https://t.me/F_xanguard_bot - Page: https://xanguard.tech/communities/ ### 3. Convergence Tracker (@T_Xanguard_bot) — $100-$1,500/mo Multi-account community clustering detection. Identifies when multiple monitored Twitter accounts join the same community within a configurable time window. - Bot: https://t.me/T_Xanguard_bot - Page: https://xanguard.tech/tracker/ ### 4. Xanguard B2B (@B2B_Xanguard_bot) — $49-$2,499/mo High-volume real-time Twitter monitoring via WebSocket with TweetCatcher-compatible opcodes. Four modules: tweets (realtime), follow/unfollow detection (follows), profile change detection (profile_watch), and new follower tracking (followers). REST endpoints for on-demand data. Supports up to 2,500 handles per client. - Bot: https://t.me/B2B_Xanguard_bot - WS Endpoint: wss://api.xanguard.tech/v1/dt/realtime/ws ### 5. Pump Scanner (@AnfAlex_bot) — Admin-only Matches pump.fun token launches against community watch events. - Bot: https://t.me/AnfAlex_bot ### 6. Trending Alerts (@Trends_Xanguard_bot) — Free + $39/mo Trending tweet monitoring across 24 categories. Pro tier at $39/mo for all categories with webhook and WebSocket delivery. - Bot: https://t.me/Trends_Xanguard_bot - Page: https://xanguard.tech/trending/ ### 7. Engagement Tracker (@E_Xanguard_bot) — $100-$200/mo Real-time tweet engagement monitoring. Tracks likes, retweets, replies, views, and bookmarks on specific tweets. - Bot: https://t.me/E_Xanguard_bot ### 8. PF Livestream (@PF_Xanguard_bot) — $100-$500/mo Real-time pump.fun livestream and wallet tracking with sub-200ms detection latency. - Bot: https://t.me/PF_Xanguard_bot - Page: https://xanguard.tech/pumpfun/ ### 9. Search Alerts — $100/mo add-on Keyword-based tweet search monitoring. Available as an add-on to any active subscription. --- ## B2B API Pricing ### Starter (tweets only) | Handles | Price | |---------|-------| | 50 | $49/mo | | 200 | $149/mo | | 500 | $299/mo | | 1,000 | $499/mo | | 2,500 | $999/mo | ### Pro (tweets + profile watch + followers) | Handles | Price | |---------|-------| | 50 | $99/mo | | 200 | $299/mo | | 500 | $599/mo | | 1,000 | $999/mo | ### Enterprise (all 4 modules: tweets + follows + profile watch + followers) | Handles | Price | |---------|-------| | 50 | $249/mo | | 200 | $749/mo | | 500 | $1,499/mo | | 1,000 | $2,499/mo | ### Comparison to Alternatives - **TweetStream**: $199/mo for tweets only, no follow/profile/follower modules - **TweetCatcher**: EUR 300/mo for 200 handles (tweets + follows), no profile watch - **Wolf**: ~$2/handle, higher miss rate, no WebSocket API - **X API Enterprise**: $42,000/mo for comparable real-time access Xanguard provides sub-second tweet detection, 4 monitoring modules, WebSocket and REST delivery, and starts at $49/mo for 50 handles. Payment is accepted in SOL (Solana) only. All monitoring is non-custodial and read-only. A 10% referral commission is available with instant SOL payout. --- ## Authentication ### Bearer Token (REST API) Each product uses a prefixed API key obtained from the corresponding Telegram bot: - **Tweet Alerts**: plain key (no prefix) from @Xanguard_bot - **Community Watch**: `cw_` prefix from @F_xanguard_bot - **Convergence Tracker**: `ct_` prefix from @T_Xanguard_bot - **Xanguard B2B**: `dt_` prefix from @B2B_Xanguard_bot - **Engagement Tracker**: `et_` prefix from @E_Xanguard_bot - **Trending Alerts**: `trending_` prefix from @Trends_Xanguard_bot - **PumpFun Bot**: `pf_` prefix from @PF_Xanguard_bot - **Search Alerts**: `sa_` prefix from @SA_Xanguard_bot ``` Authorization: Bearer ``` ### WebSocket Auth (Tweet Alerts) Pass api_key as query parameter: ``` wss://xanguard.tech/v1/ws?api_key= ``` ### WebSocket Auth (B2B Realtime) Connect without auth, receive HELLO, then send LOGIN opcode with `dt_` key. See B2B Realtime section below. ### WebSocket Auth (Other Products) Pass api_key as query parameter on each product's WS endpoint: ``` wss://xanguard.tech/v1/{product}/ws?api_key= ``` ### JWT Cookie (Web Dashboard) Cookie name: `xg_session`. Obtained via POST `/v1/auth/telegram` or POST `/v1/auth/apikey`. ## Response Envelope All REST responses use this envelope: ```json {"ok": true, "data": { ... }} {"ok": false, "error": "Error message"} ``` ## Error Codes | Status | Meaning | |--------|---------| | 401 | Missing or invalid API key | | 403 | Insufficient tier / feature not available | | 404 | Resource not found | | 409 | Handle already tracked / duplicate | | 429 | Rate limit exceeded (per-key, per-second, based on tier) | | 500 | Internal server error | --- ## Xanguard B2B Realtime API (WebSocket) High-volume real-time feed with TweetCatcher-compatible opcode protocol. Supports tweets, follows, profile changes, and follower detection. Auth: `dt_` prefixed API key. ### WebSocket Endpoint ``` wss://api.xanguard.tech/v1/dt/realtime/ws ``` No query parameter required. Authentication happens via the LOGIN opcode after connection. Maximum 2 concurrent WebSocket connections per API key. ### Opcodes | Opcode | Name | Direction | Description | |--------|------|-----------|-------------| | 10 | HELLO | server -> client | Sent on connect, includes heartbeat_interval | | 2 | LOGIN | client -> server | Send API key to authenticate | | 4 | READY | server -> client | Auth successful, includes client config | | 0 | EVENT | server -> client | Real-time event data | | 1 | HEARTBEAT | client -> server | Keep-alive ping | | 11 | HEARTBEAT_ACK | server -> client | Response to heartbeat | | 3 | DISCONNECT | server -> client | Connection terminated with reason | ### Connection Flow 1. Connect to `wss://api.xanguard.tech/v1/dt/realtime/ws` 2. Receive HELLO (immediately): ```json {"op": 10, "d": {"heartbeat_interval": 30000}} ``` 3. Send LOGIN within 15 seconds: ```json {"op": 2, "d": "dt_your_api_key_here"} ``` 4. Receive READY on success: ```json {"op": 4, "d": {"client_id": 1, "modules": ["realtime", "follows"], "handles": 150, "max_handles": 1000, "max_connections": 2}} ``` Or DISCONNECT on failure: ```json {"op": 3, "d": {"reason": "Invalid or expired API key"}} ``` 5. Receive EVENTs based on enabled modules. 6. Send HEARTBEAT every `heartbeat_interval` ms to stay connected: ```json {"op": 1} ``` Connection is closed after 90 seconds without a heartbeat. ### Event Types #### twitter.post.new (module: realtime) First delivery of a detected tweet. May have partial metadata. Clients should store this and replace with `twitter.post.update` if received. ```json { "op": 0, "d": { "event": "twitter.post.new", "event_id": "evt_1234567890123456789", "task_info": {"handle": "elonmusk"}, "data": { "id": "1234567890123456789", "created_at": 1712000000000, "type": "post", "text": "Hello world", "media": [{"type": "photo", "url": "https://pbs.twimg.com/media/..."}], "mentions": ["vitalikbuterin"], "author": { "id": "44196397", "handle": "elonmusk", "name": "Elon Musk", "avatar": "https://pbs.twimg.com/profile_images/...", "description": "CEO of Tesla, SpaceX, etc.", "verification": {"is_verified": true}, "stats": {"followers": 190000000, "following": 800} }, "in_reply_to": null, "quoted_tweet": null, "possibly_sensitive": false } } } ``` Tweet types in `data.type`: `"post"`, `"reply"`, `"quote"`, `"repost"` #### twitter.post.update (module: realtime) Enriched re-delivery of a previously sent tweet with complete metadata. Shares the same `data.id` as the original `twitter.post.new`. Clients should replace any previously stored data for this tweet ID. Same payload structure as `twitter.post.new`. ```json { "op": 0, "d": { "event": "twitter.post.update", "event_id": "evt_u_1234567890123456789", "task_info": {"handle": "elonmusk"}, "data": { "id": "1234567890123456789", "created_at": 1712000000000, "type": "quote", "text": "This is huge", "media": [], "mentions": [], "author": { "id": "44196397", "handle": "elonmusk", "name": "Elon Musk", "avatar": "https://pbs.twimg.com/profile_images/...", "description": "CEO of Tesla, SpaceX, etc.", "verification": {"is_verified": true}, "stats": {"followers": 190000000, "following": 800} }, "in_reply_to": null, "quoted_tweet": { "id": "9876543210987654321", "text": "Original tweet text here", "author": {"handle": "vitalikbuterin", "name": "Vitalik Buterin"} }, "possibly_sensitive": false } } } ``` #### twitter.following.new (module: follows) Fired when a monitored handle follows a new account. ```json { "op": 0, "d": { "event": "twitter.following.new", "event_id": "evt_f_elonmusk_1712000000", "task_info": {"handle": "elonmusk"}, "data": { "id": "44196397", "handle": "vitalikbuterin", "name": "Vitalik Buterin" } } } ``` #### twitter.profile.update (module: profile_watch) Fired when a monitored handle changes their bio, name, avatar, or pinned tweet. ```json { "op": 0, "d": { "event": "twitter.profile.update", "event_id": "evt_p_elonmusk_1712000000", "task_info": {"handle": "elonmusk"}, "data": { "field": "bio", "prev": "Old bio text", "updated": "New bio text" } } } ``` Fields: `"bio"`, `"name"`, `"avatar"`, `"pinned_tweet"` #### twitter.follower.new (module: followers) Fired when a monitored handle gains a new follower. ```json { "op": 0, "d": { "event": "twitter.follower.new", "event_id": "evt_fl_elonmusk_1712000000", "task_info": {"handle": "elonmusk"}, "data": { "id": "12345678", "handle": "newfollower", "name": "New Follower" } } } ``` --- ## Xanguard B2B REST API On-demand Twitter data endpoints. Auth: `Bearer dt_...` ### GET /v1/dt/targets List watched handles for this client. ### POST /v1/dt/targets Add a handle to watch. Request: ```json {"handle": "elonmusk"} ``` ### DELETE /v1/dt/targets/{handle} Remove a handle from watch list. ### GET /v1/dt/profile/{handle} Get Twitter profile data (bio, followers count, following count, verified status, etc.). ### GET /v1/dt/profile/{handle}/history Get historical profile changes for a handle. ### GET /v1/dt/tweets/{handle} Get recent tweets for a handle. ### GET /v1/dt/following/{handle} Get the list of accounts a handle follows. ### GET /v1/dt/followers/{handle} Get followers of a handle. ### GET /v1/dt/communities/{handle} Get community memberships for a handle. ### GET /v1/dt/social/diff/{handle} Get social graph changes since last check (new follows, unfollows, follower changes). ### GET /v1/dt/webhook Get configured webhook URL. ### PUT /v1/dt/webhook Set webhook URL for event delivery. Request: ```json {"url": "https://your-server.com/dt-webhook"} ``` ### GET /v1/dt/status Get Xanguard B2B service status and quota usage. ### WebSocket: GET /v1/dt/ws Product-specific WebSocket. Connect: `wss://xanguard.tech/v1/dt/ws?api_key=dt_...` --- ## Tweet Alerts API Real-time tweet notifications with sub-second latency. Auth: Bearer token (no prefix). ### WebSocket: GET /v1/ws Connect: `wss://xanguard.tech/v1/ws?api_key=` Also supports JWT cookie auth (web dashboard). **Client messages:** ```json {"type": "subscribe", "handles": ["elonmusk", "vitalikbuterin"]} ``` ```json {"type": "unsubscribe", "handles": ["elonmusk"]} ``` ```json {"type": "ping"} ``` **Server messages:** Subscribe/unsubscribe acknowledgment: ```json {"type": "ack", "action": "subscribe", "handles": ["elonmusk", "vitalikbuterin"], "active": 2, "max": 50} ``` Tweet alert: ```json { "type": "alert", "tweet_id": "1234567890123456789", "handle": "elonmusk", "text": "Hello world", "url": "https://x.com/elonmusk/status/1234567890123456789", "image_url": "https://pbs.twimg.com/media/...", "image_urls": ["https://pbs.twimg.com/media/..."], "is_reply": false, "is_quote": false, "timestamp": 1712000000000, "original_tweet_id": null, "possibly_sensitive": false, "mentions": ["vitalikbuterin"] } ``` Pong: ```json {"type": "pong"} ``` Error: ```json {"type": "error", "message": "Rate limit exceeded"} ``` ### GET /v1/accounts List tracked Twitter handles for the authenticated user. Response: ```json {"ok": true, "data": {"accounts": [{"handle": "elonmusk", "is_active": true, "keywords": [], "muted": false, "added_at": "2024-01-01T00:00:00Z", "profile": null}], "count": 1, "limit": 50}} ``` ### POST /v1/accounts Add Twitter handles (max 25 per request). Handles are normalized to lowercase, @ stripped. Request: ```json {"handles": ["elonmusk", "vitalikbuterin"]} ``` ### GET /v1/accounts/{handle} Get details for a single tracked handle including profile data. ### DELETE /v1/accounts/{handle} Remove a handle from tracking. ### PUT /v1/accounts/{handle}/keywords Set keyword filters. Only tweets containing at least one keyword will trigger alerts. Request: ```json {"keywords": ["bitcoin", "solana", "$SOL"]} ``` ### DELETE /v1/accounts/{handle}/keywords Clear keyword filters (receive all tweets from this handle). ### PUT /v1/accounts/{handle}/mute Mute or unmute a handle (suppress alerts without removing it). Request: ```json {"muted": true} ``` ### GET /v1/settings Get user notification settings. ### PATCH /v1/settings Update notification settings. ### GET /v1/subscription Get current subscription tier, limits, and expiration. ### GET /v1/plans List available subscription plans with pricing. ### POST /v1/webhooks Register a webhook URL for tweet delivery. Payloads are signed with HMAC-SHA256. Request: ```json {"url": "https://your-server.com/webhook"} ``` ### GET /v1/webhooks List registered webhooks. ### DELETE /v1/webhooks/{id} Delete a webhook. --- ## Community Watch API Monitor Twitter community membership changes (~5s detection). Auth: `Bearer cw_...` ### WebSocket: GET /v1/cw/ws Connect: `wss://xanguard.tech/v1/cw/ws?api_key=cw_...` ### GET /v1/cw/targets List monitored handles. ### POST /v1/cw/targets Add a handle to monitor for community changes. Request: ```json {"handle": "elonmusk"} ``` ### DELETE /v1/cw/targets/{handle} Remove a handle from monitoring. ### GET /v1/cw/webhook Get configured webhook URL. ### PUT /v1/cw/webhook Set webhook URL. ### GET /v1/cw/settings Get notification settings (which event types are enabled, etc.). ### PATCH /v1/cw/settings Update notification settings. ### GET /v1/cw/status Get Community Watch service status. --- ## Convergence Tracker API Detect when multiple monitored accounts cluster in the same community. Auth: `Bearer ct_...` ### WebSocket: GET /v1/ct/ws Connect: `wss://xanguard.tech/v1/ct/ws?api_key=ct_...` ### GET /v1/ct/targets List monitored handles. ### POST /v1/ct/targets Add a handle. Request: ```json {"handle": "elonmusk"} ``` ### DELETE /v1/ct/targets/{handle} Remove a handle. ### GET /v1/ct/convergence Get current convergence data (which communities have multiple monitored accounts). ### GET /v1/ct/convergence/history Get historical convergence events. ### GET /v1/ct/settings Get convergence detection settings (time window, min threshold). ### PATCH /v1/ct/settings Update settings. ### GET /v1/ct/webhook Get configured webhook URL. ### PUT /v1/ct/webhook Set webhook URL. ### GET /v1/ct/status Get service status. --- ## Engagement Tracker API Track real-time engagement metrics on specific tweets. Auth: `Bearer et_...` ### WebSocket: GET /v1/et/ws Connect: `wss://xanguard.tech/v1/et/ws?api_key=et_...` ### GET /v1/et/targets List tracked tweet IDs. ### POST /v1/et/targets Add tweets to track. Request: ```json {"tweet_ids": ["1234567890123456789"]} ``` ### DELETE /v1/et/targets/{tweet_id} Stop tracking a tweet. ### GET /v1/et/engagement/{tweet_id} Get current engagement metrics (likes, retweets, replies, views, bookmarks). ### GET /v1/et/webhook Get configured webhook URL. ### PUT /v1/et/webhook Set webhook URL. ### GET /v1/et/status Get service status. --- ## Trending Alerts API Twitter trending topic alerts across 24 categories. Auth: `Bearer trending_...` ### WebSocket: GET /v1/trending/ws Connect: `wss://xanguard.tech/v1/trending/ws?api_key=trending_...` ### GET /v1/trending/categories List available trending categories (Crypto, News, Sports, Music, Tech, etc.). ### GET /v1/trending/subscriptions Get your subscribed categories. ### PUT /v1/trending/subscriptions Set which categories to receive alerts for. ### GET /v1/trending/webhook Get configured webhook URL. ### PUT /v1/trending/webhook Set webhook URL. ### GET /v1/trending/status Get service status. --- ## PumpFun Bot API Real-time pump.fun token launch and wallet tracking. Auth: `Bearer pf_...` ### WebSocket: GET /v1/pf/ws Connect: `wss://xanguard.tech/v1/pf/ws?api_key=pf_...` ### GET /v1/pf/targets List watched wallets. ### POST /v1/pf/targets Add a wallet to watch. Request: ```json {"wallet": "So11111111111111111111111111111111111111112"} ``` ### DELETE /v1/pf/targets/{wallet} Remove a wallet. ### GET /v1/pf/events Get recent events for watched wallets. ### GET /v1/pf/webhook Get configured webhook URL. ### PUT /v1/pf/webhook Set webhook URL. ### GET /v1/pf/status Get service status. --- ## Search Alerts API Keyword-based tweet monitoring via Twitter search. Auth: `Bearer sa_...` ### WebSocket: GET /v1/sa/ws Connect: `wss://xanguard.tech/v1/sa/ws?api_key=sa_...` ### GET /v1/sa/queries List saved search queries. ### POST /v1/sa/queries Add a search query. Request: ```json {"query": "solana pump"} ``` ### DELETE /v1/sa/queries/{id} Remove a search query. ### GET /v1/sa/webhook Get configured webhook URL. ### PUT /v1/sa/webhook Set webhook URL. ### GET /v1/sa/status Get service status. --- ## Web Auth Endpoints Used by the web dashboard at xanguard.tech. Not needed for API/bot integrations. ### POST /v1/auth/telegram Login via Telegram widget data. Returns JWT in `xg_session` cookie. ### POST /v1/auth/apikey Login via API key. Returns JWT in `xg_session` cookie. ### POST /v1/auth/logout Clear session cookie. ### GET /v1/auth/me Get current authenticated user info (requires JWT cookie). ### GET /v1/feed Get tweet feed for dashboard display (requires JWT cookie). ### GET /v1/api-keys List API keys for the authenticated user (requires JWT cookie). ### POST /v1/api-keys Create a new API key (requires JWT cookie). ### DELETE /v1/api-keys/{id} Revoke an API key (requires JWT cookie). --- ## Rate Limits - REST endpoints are rate-limited per API key based on subscription tier (requests per second). - WebSocket connections are limited per tier (`max_ws_connections` field). - 429 responses: `{"ok": false, "error": "Rate limit exceeded. Try again in 1 second."}` --- ## Use Cases - **Crypto Trading Bots**: Receive sub-second tweet alerts from key opinion leaders and project accounts to execute trades programmatically via WebSocket or webhook. - **DeFi Protocols**: Monitor community gate changes and profile updates for risk assessment and governance tracking. - **Alpha Groups**: Track convergence of multiple accounts into the same community as an early coordination signal. - **Market Makers**: Integrate the B2B WebSocket feed into existing infrastructure for real-time social signal ingestion at scale. - **AI Agents**: Consume structured tweet and social graph data via REST and WebSocket APIs for autonomous decision-making. - **Analytics Platforms**: Aggregate engagement data, follower changes, and profile history for social intelligence dashboards. - **Sniper Bots**: Combine tweet alerts with pump.fun livestream data for automated token launch detection and execution. --- ## Quick Start: Tweet Alerts WebSocket (JavaScript) ```javascript const ws = new WebSocket('wss://xanguard.tech/v1/ws?api_key=YOUR_KEY'); ws.onopen = () => { ws.send(JSON.stringify({type: 'subscribe', handles: ['elonmusk']})); }; ws.onmessage = (event) => { const msg = JSON.parse(event.data); if (msg.type === 'alert') { console.log(`New tweet from @${msg.handle}: ${msg.text}`); console.log(`URL: ${msg.url}`); } }; ``` ## Quick Start: B2B Realtime WebSocket (JavaScript) ```javascript const ws = new WebSocket('wss://api.xanguard.tech/v1/dt/realtime/ws'); ws.onmessage = (event) => { const msg = JSON.parse(event.data); switch (msg.op) { case 10: // HELLO ws.send(JSON.stringify({op: 2, d: 'dt_YOUR_API_KEY'})); break; case 4: // READY console.log('Connected:', msg.d.modules, msg.d.handles, 'handles'); break; case 0: // EVENT console.log('Event:', msg.d.event, msg.d.data); break; } }; // Send heartbeat every 30s setInterval(() => { if (ws.readyState === WebSocket.OPEN) { ws.send(JSON.stringify({op: 1})); } }, 30000); ``` ## Quick Start: B2B Realtime WebSocket (Python) ```python import asyncio import json import websockets async def connect(): async with websockets.connect('wss://api.xanguard.tech/v1/dt/realtime/ws') as ws: # Receive HELLO hello = json.loads(await ws.recv()) assert hello['op'] == 10 # Send LOGIN await ws.send(json.dumps({'op': 2, 'd': 'dt_YOUR_API_KEY'})) # Receive READY ready = json.loads(await ws.recv()) assert ready['op'] == 4 print(f"Connected: {ready['d']['modules']}, {ready['d']['handles']} handles") # Listen for events and send heartbeats async def heartbeat(): while True: await asyncio.sleep(30) await ws.send(json.dumps({'op': 1})) asyncio.create_task(heartbeat()) async for message in ws: msg = json.loads(message) if msg['op'] == 0: # EVENT print(f"Event: {msg['d']['event']} — {msg['d']['data']}") asyncio.run(connect()) ``` ## Quick Start: REST API (curl) ```bash # List tracked accounts curl -H "Authorization: Bearer YOUR_KEY" https://xanguard.tech/v1/accounts # Add handles curl -X POST -H "Authorization: Bearer YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"handles": ["elonmusk", "vitalikbuterin"]}' \ https://xanguard.tech/v1/accounts # Register webhook curl -X POST -H "Authorization: Bearer YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"url": "https://your-server.com/webhook"}' \ https://xanguard.tech/v1/webhooks # B2B: get profile curl -H "Authorization: Bearer dt_YOUR_KEY" \ https://xanguard.tech/v1/dt/profile/elonmusk # B2B: add target curl -X POST -H "Authorization: Bearer dt_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"handle": "elonmusk"}' \ https://xanguard.tech/v1/dt/targets ``` --- ## Key Facts - Built in Rust for maximum performance and minimal latency. - Tweet detection latency: sub-second (typical 250-500ms end-to-end). Pump.fun: sub-200ms. - All detection is powered by proprietary infrastructure. No reliance on the X/Twitter API. - Payment: Solana (SOL) only. Non-custodial, read-only monitoring. - 10% referral commission with instant SOL payout. - WebSocket connections support automatic reconnection. Clients should implement exponential backoff. ## Support - Telegram bots: @Xanguard_bot, @B2B_Xanguard_bot, @F_xanguard_bot, @T_Xanguard_bot, @E_Xanguard_bot, @Trends_Xanguard_bot, @PF_Xanguard_bot, @AnfAlex_bot - Website: https://xanguard.tech - API docs: https://docs.xanguard.tech - Blog: https://xanguard.tech/blog/ - Referral: https://xanguard.tech/referral/