Live API Benchmark
Blockchain Data API Comparison
Comparing GoldRush, Alchemy, Mobula, and Codex across multiple data endpoints
OHLCV Data Architecture Comparison
Each provider tested with their available OHLCV method
| Provider | Historical | Live Updates | Connections | Pair InfoIncluded in OHLCV response. Others need separate API call. | USD VolIncluded in OHLCV response. Others need price API conversion. |
|---|---|---|---|---|---|
| Mobula | REST API | Separate WebSocket | 2 connections | ||
| Codex | GraphQL Query | Separate WebSocket | 2 connections | ||
| GoldRush | WebSocket | Same WebSocket | 1 connection |
Methodology
Test: Fetch historical OHLCV candlestick data for a DEX trading pair on Ethereum mainnet.
Fairness: Each provider is tested using their only available method for historical OHLCV data. GoldRush provides OHLCV exclusively via streaming - there is no REST endpoint. Mobula/Codex WebSockets only send live updates, requiring REST/GraphQL for historical data.
Metrics: Latency, candle count, volume data, delivery method, and connection architecture.
Note: Alchemy does not provide OHLCV candlestick data - only simple price points.
Key Insight: GoldRush's streaming-only architecture means you get historical + live OHLCV data in 1 WebSocket connection. With Mobula/Codex, building a real-time trading app requires 2 separate connections (REST for backfill + WebSocket for live).
Pricing & Limits
| Provider | Free Tier | Rate Limit | Chains |
|---|---|---|---|
| GoldRush | 25,000 credits/month | 4 req/sec | 100+ |
| Alchemy | 30M compute units/month | 500 CUs/sec | 80+ |
| Mobula | 10,000 credits/month | No limit | 30+ |
| Codex | 10,000 req/month (no balances) | 5 req/sec | 80+ |