SocialData (socialdata.tools) is a pay-per-read X data API: $0.20 per 1,000 tweets or profiles, plus webhook monitors that deliver up to 30 seconds after a change. If you need sub-second posts from a fixed list of accounts, the alternative is a stream: Xanguard sends new tweets, deleted tweets, profile changes and follows over one WebSocket, median detection under 250 ms, from $49 a month for 50 accounts. SocialData facts read on its own site and docs on 20 November 2026.
SocialData API pricing (checked 20 November 2026)
| Item | SocialData price |
|---|---|
| Tweets or user profiles returned | $0.0002 each ($0.20 per 1,000) |
| Extended bio | $0.001 per request |
| Verify a user follows another | $0.004 per request |
| Verify a retweet or comment | $0.008 per request |
| User monitors (tweets, following, profile) | $0.0069/hour each for 1-10 (about $4.99/mo), $0.0062 for 11-100 (about $4.49), $0.0055 for 101-300 (about $3.99), $0.0048 for 301-500 (about $3.49), $0.0042 for 501-1,000 (about $2.99), $0.0035 above 1,000 (about $2.49) |
| Search monitors | $0.0002 per tweet delivered, $0.0002 per empty run; at the default 30-second refresh, at least about $17.28 a month |
| Free plan | None; no card needed to sign up; up to 3 requests a minute free under fair use |
| Rate limit | 120 requests a minute per user, higher on request |
| Platforms | X only |
Sources: pricing, monitoring pricing, monitoring introduction, rate limits. We did not find payment methods or a minimum top-up on the pages we read.
SocialData vs Xanguard
| SocialData | Xanguard B2B | |
|---|---|---|
| Model | REST reads, plus webhook monitors | WebSocket stream for a list of accounts, plus REST to manage the list |
| Delivery speed | Monitors: up to 30 seconds, "not the right tool" for sub-second | Median tweet detection under 250 ms, published hourly |
| New posts from an account | User Tweets monitor | twitter.post.new, every plan |
| Deleted posts | Not listed among monitor types | twitter.tweet.deleted with the last-seen text, every plan |
| New follows by an account | User Following monitor | twitter.following.new, Enterprise |
| Unfollows | Not mentioned | twitter.following.removed, Enterprise |
| Profile changes | Name, bio, location, website, profile image | Bio, name, avatar, banner, location, website, verified badge, pinned post and handle, Pro |
| New followers of an account | Not listed | twitter.follower.new, Pro |
| Keyword or search monitors | Yes | No (stream is per account) |
| Search, history, bulk lookups | Yes | No |
| MCP server | Yes, read-only, 14 tools | No |
| Price for 50 accounts watched | About $225 a month in user monitors (tweets only) | $49 a month (tweets and deleted tweets) |
| Payment | Not stated on the pages we read | SOL, activates automatically |
When SocialData is the better choice
- You need search or history. Xanguard has no search API and no archive.
- You do bulk lookups. $0.20 per 1,000 profiles or tweets is cheap for research jobs.
- A 30-second delay is fine and you watch a handful of accounts or keyword queries.
- You want an MCP server for an AI assistant to read X data.
When Xanguard is the better choice
- Speed matters. Trading bots, terminals and alert products need the post in well under a second.
- You watch many accounts. 250 accounts cost $229 a month on Xanguard Starter against about $998 in SocialData user monitors.
- You need deletions and unfollows. Both are on the Xanguard stream.
- You want one connection for tweets, deletes, profile changes and follows instead of one monitor per account per event type.
Other SocialData alternatives (checked 20 November 2026)
| Provider | What it sells | Published price |
|---|---|---|
| Xanguard | Real-time WebSocket stream for listed accounts | $49/mo for 50 accounts, $849 for 1,000 |
| twitterapi.io | REST reads; separate account stream | $0.15 per 1,000 tweets; stream $29/mo for 6 accounts to $999 for 2,000 |
| Apify Tweet Scraper (apidojo) | Batch scraping actor | From $0.40 per 1,000 tweets |
| TweetAPI | REST, billed in API units | $17/mo for 100,000 units; 100 free units |
| Official X API | Pay-per-use reads, filtered stream, Activity API | $0.005 per post read ($5 per 1,000) |
Full cost breakdown: X API cost in 2026. Coming from twitterapi.io: twitterapi.io alternatives.
Moving SocialData user monitors to Xanguard
- Get a key in @B2B_Xanguard_bot and pick a plan for your account count.
- For each user monitor, add the account once:
POST https://api.xanguard.tech/v1/dt/targetswith{"handle": "username"}. One handle covers every event type your plan includes. - Replace your webhook receiver with a WebSocket client, or keep the receiver and forward to it:
# Python: forward Xanguard stream events to the webhook handler you already run
import asyncio, json, requests, websockets
URL, KEY = "wss://api.xanguard.tech/v1/dt/realtime/ws", "dt_YOUR_API_KEY"
HOOK = "http://localhost:8080/x-events" # your existing receiver
async def main():
async with websockets.connect(URL) as ws:
hello = json.loads(await ws.recv())
await ws.send(json.dumps({"op": 2, "d": KEY}))
async def beat():
while True:
await asyncio.sleep(hello["d"]["heartbeat_interval"] / 1000)
await ws.send(json.dumps({"op": 1}))
hb = asyncio.create_task(beat())
async for raw in ws:
m = json.loads(raw)
if m["op"] == 0: # twitter.post.new, twitter.tweet.deleted, twitter.following.new ...
requests.post(HOOK, json=m["d"], timeout=5)
hb.cancel()
asyncio.run(main())
Production clients should reconnect with backoff: see the B2B WebSocket docs and the Python client guide. Replacing X's own stream instead? See the filtered stream alternative.
Xanguard B2B pricing
| Accounts | Starter (tweets + deleted tweets) | Pro (+ profile changes, new followers) | Enterprise (+ follows and unfollows, image OCR) |
|---|---|---|---|
| 50 | $49/mo | $99/mo | $249/mo |
| 250 | $229/mo | $429/mo | $979/mo |
| 500 | $449/mo | $749/mo | $1,649/mo |
| 1,000 | $849/mo | $1,349/mo | $2,849/mo |
Paid in SOL in @B2B_Xanguard_bot; the plan activates automatically when the payment confirms. Prices from the live plan list on 20 November 2026.
Frequently Asked Questions
SocialData's docs list $0.0002 per tweet or user profile returned, or $0.20 per 1,000 items, with a few endpoints priced per request (for example $0.004 to verify a follow). User monitors cost $0.0069 an hour each for 1 to 10 monitors (about $4.99 a month), falling to $0.0035 an hour (about $2.49) above 1,000. Checked 20 November 2026.
No. Its homepage FAQ says it does not currently offer a free plan and invites you to contact support; signup needs no credit card. Every account gets up to 3 requests a minute without charge under its fair-use rule (checked 20 November 2026).
Its monitors deliver by webhook up to 30 seconds after a change on X, usually faster, and the docs say: if your use case depends on sub-second reaction, the Monitoring API is not the right tool today. Xanguard's WebSocket stream publishes a median tweet detection under 250 ms at xanguard.tech/speed.
For real-time posts, deletions, profile changes and follows from a list of X accounts, Xanguard: a WebSocket stream from $49 a month for 50 accounts. For cheaper bulk reads, twitterapi.io lists $0.15 per 1,000 tweets. For one-off scraping jobs, Apify's Tweet Scraper starts at $0.40 per 1,000 tweets.
For user monitors, yes: new posts (every plan), profile changes (Pro) and new follows (Enterprise) arrive on one WebSocket, plus deleted tweets and unfollows, which SocialData's monitor list does not mention. For search-query monitors and REST lookups, no: Xanguard has no search or history API.
The B2B API delivers over WebSocket, not webhooks. Signed webhooks exist on paid Tweet Alerts plans, a separate product. If your system expects a webhook, a small WebSocket client that POSTs each event to your endpoint does the same job.