Learn how to use the Insight oracle data platform for real-time price monitoring, multi-dimensional price comparison, and deep data analysis.
Get started with Insight in just a few steps
Insight aggregates price data from 10 oracle providers across 54+ blockchains to provide comprehensive market insights, consensus pricing, and oracle reliability analysis.
Select an oracle provider, blockchain, and token to get real-time prices with on-chain data
Cross-oracle comparison with consensus price, cross-chain analysis with heatmap, and reputation scores
Track oracle reputation over time and monitor price deviations
Explore all the features Insight has to offer
Query real-time prices from any oracle provider with on-chain data, confidence intervals, and auto-refresh
Compare oracle prices across providers and blockchains with consensus price, divergence signals, and risk analysis
Persistent 7-day rolling reputation scores with accuracy, uptime, reliability, latency, and freshness metrics
Real-time Updates
Live data with auto-refresh
10 Oracle Providers
Chainlink, Pyth, API3, RedStone, DIA, and more
Multi-format Export
CSV, JSON, Excel, PDF, PNG
Deep dive into our technical implementation and architecture
Learn about our data collection, validation methodology, and consensus algorithms
Learn about our internal API architecture and data flow between oracle providers
Next.js App Router with Supabase, React Query, Zustand, and 10 oracle client implementations
10 oracle providers including Chainlink, Pyth, API3, RedStone, DIA, WINkLink, Supra, TWAP, Reflector, and Flare
Integration guides and technical support for developers.
We support 10 oracle providers: chainlink, pyth, api3, redstone, dia, winklink, supra, twap, reflector, and flare. Each provider may support different blockchains and trading pairs.
We support 4 consensus methods: median, trimmed_mean, weighted_median, and iqr_filtered. The best method is auto-selected based on data characteristics.
Symbols containing "/" must be URL-encoded. For example, BTC/USD should be sent as BTC%2FUSD in the URL path.
Historical data is provider-specific and cannot be aggregated across oracles. You must specify which oracle provider to query, e.g., ?provider=chainlink.