Skip to main content
Scrapest delivers Twitter/X data faster, cheaper, and with zero rate limits compared to the official X API. Here’s how they compare.
Live benchmarks are available at benchmark.scrape.st — updated in real-time.

​
At a Glance

MetricScrapestX API (Official)
Median Latency~450ms from post5-15s (search index lag)
P95 Latency~1.2s30s+
Rate LimitsNone100-500 req/15min
Monthly CostUsage-based100−100 - 5,000+/mo
Real-time Streaming✅ WebSocket + SSE❌ (Enterprise only $42k+)
Telegram & Discord✅ Built-in❌ Not available
Backfill History✅ On-demand⚠️ Limited (7-day window)
Token/Cashtag Search✅ Optimized⚠️ Generic search only

​
What We Measure

​
Latency

Time from when a post is created on the source platform to when Scrapest delivers it to your webhook/stream. Measured end-to-end across all 3 web-push shards.
  • Source Latency — Platform → Scrapest ingestion
  • Internal Latency — Scrapest processing → webhook/stream delivery
  • P50 / P95 / P99 — Percentile distribution over a 24-hour rolling window

​
Coverage

Scrapest tracks 3,000+ accounts simultaneously across Twitter/X with zero rate-limit throttling, using a distributed account pool with geographic proxy distribution (GB/US/KW).

​
Latency Comparison

​
Scrapest

{
  "source_latency_ms": { "p50": 50, "p95": 120, "p99": 500 },
  "internal_latency_ms": { "p50": 48, "p95": 58, "p99": 60 }
}

​
X API (Official)

The official X API v2 search endpoint has index lag of 5-15 seconds. Filtered stream (Enterprise only at $42,000+/year) claims ~seconds latency but is inaccessible to most developers.
X API TierPrice/moTweet CapSearchStream
Free$01,500 reads❌❌
Basic$10010,000 reads❌❌
Pro$5,0001M reads✅❌
Enterprise$42,000+Unlimited✅✅

​
Cost Comparison

For a typical integration tracking 100 accounts with real-time delivery:
RequirementScrapestX API
Track 100 accounts real-time✅ Included❌ Enterprise only
Search tweets by keyword✅ IncludedPro ($5,000/mo)
Webhook delivery✅ Built-in❌ Not available
Historical backfill✅ On-demandPro+ (limited)
Telegram + Discord✅ Same API❌ Separate services

​
Live Metrics

Query real-time latency data directly from the API: 
# Aggregated metrics (all sources)
curl https://scrape.st/metrics

# Twitter-specific metrics
curl https://scrape.st/metrics/twitter

# Telegram-specific metrics
curl https://scrape.st/metrics/telegram

# Discord-specific metrics
curl https://scrape.st/metrics/discord
Metrics endpoints are public — no authentication required. All data uses a 24-hour rolling window.

​
Why It Matters

  • Trading bots need sub-second latency — Scrapest delivers in ~450ms vs X API’s 5-15s
  • Social analytics need full coverage — Scrapest has zero rate limits vs X’s 100-500 req/15min caps
  • Multi-platform monitoring — one API for Twitter, Telegram, and Discord instead of 3 separate integrations
Get started: Core · REST API · Streams