Insight documentation · Product logic, risk methodology, architecture, data sources, and integration references
Follow an oracle price from collection through consensus, health analysis, risk interpretation, and signed verification. Then connect the same evidence to your application or agent.
Index — Documentation map
Start with a task, inspect the method behind it, then move into the implementation reference when you are ready to integrate.
Get started with Insight in three steps. The platform aggregates price data from major oracle providers across 40+ blockchain networks for comprehensive market intelligence.
Select an oracle provider, blockchain, and token to get current prices with on-chain verification metadata.
Cross-oracle comparison with consensus price, cross-chain heatmap, and divergence signals.
Track oracle reputation over time and track stablecoin or wrapped-asset depeg risks.
Explore the core capabilities of the Insight oracle data platform.
Inspect oracle evidence, assess a proposed action, monitor changing conditions, and retain optional verifiable assessment records.
Calculate the exact oracle price deviation that would trigger liquidation for your DeFi lending positions across multiple protocols.
Always-on cross-oracle trust signal (NORMAL / CAUTION / DANGER) that AI agents running long-lived strategies can poll and gate on between trades.
Assess stablecoins, wrapped assets, and liquid-staking tokens in one shared risk view.
Query current 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.
Daily aggregated oracle market snapshots with consensus prices, provider rankings, and unified Peg Risk highlights.
Auto-Refresh
Live on-demand price polling
10 Oracle Providers
Chainlink, API3, RedStone, DIA, and more
Safety & Risk
Position, stablecoin, and wrapped asset tracking
Multi-format Export
CSV, JSON, Excel, PDF, PNG
When signing is available, a pre-trade check can carry an EIP-712 attestation (v1 11 fields, v2 26, v3 27). The public verify endpoint checks the signature against the published attester key and routes by the attestation's own schemaVersion. At v3 both safety gates are recomputable from the bytes alone, because both policy constants are inside the signed struct; the constants are also pinned in a machine-readable declaration.
No install, no API key. Open /verify and the page fetches a public sample receipt plus the published key registry, then re-checks the EIP-712 signature entirely on your device using verify-insight-receipt. Insight never sees the result.
For agents and protocols that need an independent verification path, the repository includes a standalone npm package — published as verify-insight-receipt (v0.5.0). It verifies pre-trade and execution receipts, including closed-loop pairs, by recomputing the EIP-712 hashes and recovering signers locally; it does not need an API key, database access, or a network request.
# Published package (recommended)
npm install verify-insight-receipt
# Or from the Insight repository
npm install ./verifier
import { verifyReceipt } from 'verify-insight-receipt';
const result = await verifyReceipt(receipt, { keyRegistry });
if (result.code !== 'ok') {
throw new Error(result.code);
}Verification is not endorsement. A valid result proves the signed bytes and signer relationship, not that the underlying trade or verdict was correct.
# fetch a real signed sample
curl -s https://www.oracleinsight.xyz/api/v1/safety/attestation/sample \
| jq .data.attestation > receipt.json
# verify it (public, no API key)
curl -s https://www.oracleinsight.xyz/api/v1/safety/attestation/verify \
-H 'Content-Type: application/json' \
-d "{\"attestation\": $(cat receipt.json | jq -c)}"
# cross-check the pinned declaration (sha256 035144d0...)
curl -s https://www.oracleinsight.xyz/.well-known/vrt1-scale-declaration.json \
| shasum -a 256Deep dive into implementation details, data sources, and architecture.
Data collection, validation rules, and consensus algorithms that power Insight price intelligence.
Interactive API explorer with OpenAPI 3.1. Try endpoints live, generate code snippets, and import into Postman.
Next.js App Router with Supabase, React Query, Zustand, and 13 oracle client implementations.
13 oracle providers, independent CEX references, and separate Monad DEX execution-market evidence.
Use Robinhood Stock Token status, corporate actions, and multiplier verification without treating the issuer as an independent oracle.
Connect Claude, Cursor, and other MCP clients to oracle prices, risk summaries, pre-trade safety checks, Oracle Watch monitoring, liquidation stress tests, and more.
Use the complete execution workflow: two-sided pre-trade gates, Oracle Watch halt handling, and VERIFIED execution receipts.
Insight combines 15-minute oracle data with rigorous validation, multi-algorithm consensus, and a 7-day rolling reputation framework to produce reliable cross-provider price intelligence.
Prices are fetched from 10 oracle providers across 40+ blockchains. Each request reads either an on-chain contract or a verified API endpoint, then normalizes the result into a common PriceData structure that includes price, timestamp, decimals, confidence, and verification metadata.
Every raw price is validated before entering consensus or storage. Failures are not silently dropped; they are classified so the reputation system can distinguish between stale data, network errors, unsupported symbols, and fallback metadata.
Four consensus methods are computed for every symbol. The recommended method is chosen automatically based on asset category: stablecoins, major assets, altcoins, and micro-cap assets each get the method best suited to their typical volatility and provider coverage.
Middle value of sorted prices. Robust against extreme outliers when provider coverage is limited.
Mean after removing the top and bottom 25% of prices. Balances outlier resistance with responsiveness.
Median weighted by provider confidence (40%), price freshness (35%), and confidence-interval tightness (25%).
Removes outliers outside the interquartile range, then takes the median. Ideal for tight peg tracking.
Outliers are detected using Z-score over 2.5 standard deviations, dual-source arbitration when only two prices exist, and history-aware checks against the last 10 consensus points. Excluded providers are surfaced in the divergence UI and used to adjust confidence scoring.
Provider reputation is recomputed hourly from a 7-day rolling window of sampled price fetches. Each provider is benchmarked against a latency baseline that depends on whether it is an on-chain or API provider, so slower on-chain calls are not unfairly penalized.
Measures how close a provider's price is to the consensus. Scored as 100 − min(|deviation| × 15, 85), with a consistency bonus for low deviation variance.
Percentage of successful price fetches over a 7-day rolling window. Failed fetches are classified by failure mode for debugging.
Penalizes large deviations more aggressively than Accuracy (100 − min(|deviation| × 20, 80)). Same consistency bonus applies.
Scores how recently the on-chain / API data was updated. Degrades by 4 points per minute of stale data, capped at 90 points lost.
Response time against a provider-type baseline: on-chain providers typically get ~1,000 ms, API providers ~350–500 ms.
Average absolute deviation from consensus, bucketed into 0.1%, 0.5%, 1%, 2%, and >2% tiers.
A sample-size factor (0.85–1.0) is applied when fewer than 100 samples exist, and a consistency bonus of up to 4 points rewards providers with low deviation variance across at least 5 successful consensus comparisons.
Insight is a full-stack oracle analytics platform built for reliability, 15-minute assessment, and multi-provider comparison across blockchains.
Server-first rendering with App Router, colocated API routes, and optimized static generation for marketing and docs pages. Client components handle interactive dashboards.
React Query caches and synchronizes server state (prices, reputations, reports). Zustand manages lightweight UI state such as auth session and user preferences.
PostgreSQL stores price records, oracle feeds, API keys, reputation history, and daily reports. Row Level Security, database functions, and cron jobs run inside the database.
A unified abstraction wraps 13 oracle providers. Each client handles chain-specific calls, retries, TTL caching, and normalization into a common PriceData format.
Public v1 endpoints expose prices, batch queries, history, and reports. Internal endpoints power the unified Peg Risk experience across stablecoins and wrapped/LST assets, plus protocol-health features.
Supabase pg_cron dispatches eight product-critical workflows through pg_net using a token encrypted in Vault. Dependency-free GitHub runners perform the heavy work, guarded native schedules provide fallback, and a 30-day ledger records completion. Vercel is not used for background compute.
| Table | Purpose |
|---|---|
| price_records | Raw and normalized prices with TTL |
| oracle_feeds | Active feed metadata per provider + chain |
| hourly_price_snapshots | Hourly-grain snapshots (upsert, 120-day retention) |
| price_snapshots | 15-min-grain snapshots for ML / anomaly detection (120-day retention) |
| reputation_history | Per-fetch samples for scoring |
| oracle_reputation | Aggregated 7-day provider scores |
| api_keys | Key-based API authentication |
| daily_reports | Generated market snapshots |
The OracleClientFactory creates singleton provider clients that inherit from BaseOracleClient. Each implementation translates provider-specific identifiers (feed addresses, price IDs, dAPI names) into the unified PriceData shape.
Collect price snapshots from all oracle feeds (dual-writes hourly + 15-min tables)
Persist the Oracle Watch credibility history and trust signal
Fetch provider samples and recompute 7-day rolling scores (GitHub Actions)
Refresh per-feed observed staleness baselines (GitHub Actions)
Backfill outcome labels for pre-trade safety checks
Sync protocol TVL from DefiLlama
Sync per-asset risk parameters from lending protocols
Index finalized Monad Uniswap V3 swaps through a durable event cursor
Re-probe deactivated feeds and revive recovered ones
Generate and persist the daily report
Grant subscription credit allowances, downgrade expired subs, clean up zombie invoices
Discover new oracle feeds from each provider’s official API
Retrain the oracle-risk ML model and trigger a Vercel redeploy
Zod schemas validate PriceData and API requests. Invalid payloads are rejected before reaching business logic.
AppError and OracleServiceError classify failures (network, timeout, unsupported symbol, stale data) for observability and retries.
Each API key carries a plan-based rate limit. Usage is logged per endpoint for billing and abuse detection.
Supabase RLS policies ensure users can only read their own API keys and profile data.
Insight aggregates price data from leading oracle providers across 40+ blockchain networks, normalizing every feed into a common format for comparison and analysis. It also maintains a separate CEX spot-market reference for oracle divergence and decision input context.
| Provider | Type | Chains |
|---|---|---|
| Chainlink | On-chain | EVM L1s & L2s |
| Pyth Core | On-chain push | Monad |
| Stork | On-chain push | Monad |
| Chronicle | On-chain push | Monad |
| API3 | On-chain dAPIs | Ethereum, Arbitrum, Base, Polygon, others |
| RedStone | API / On-chain | EVM L1s & L2s |
| DIA | API / On-chain | EVM L1s & L2s |
| WINkLink | On-chain | TRON |
| Supra DORA Push | On-chain push | Monad; API coverage elsewhere |
| TWAP | On-chain | DEX TWAP oracles |
| Reflector | On-chain | Stellar / Soroban |
| Flare | On-chain | Flare Network |
| Band Protocol | BandChain / API | BandChain v3 |
Coinbase, Kraken, and Gemini provide direct USD spot references for their supported pairs; Crypto.com adds a direct WBTC/USD market. Bitstamp and Bitfinex are optional direct USD spot sources for their supported pairs. Binance currently adds a WBTC reference derived from its WBTC/USDT and USDT/USD spot markets, so its quote-currency conversion remains explicit.
Solana-native assets (the CAIP-19 Solana registry) are priced by three Solana sources: Jupiter Lite (the documented free tier of Jupiter's price API, serving as the aggregated-liquidity baseline), plus DexScreener and GeckoTerminal, which aggregate public on-chain Solana liquidity pools — one batch request each per collection run. These quotes give every registered Solana asset a three-source cross-checkable market reference; as pool-derived prices they are treated as consensus inputs, not authoritative prints. DexScreener additionally fail-closes any pair its indexer has not seen trade in over 24 hours, so a silent pool never writes a stale reference.
Optional Bitstamp, Bitfinex, and Binance collection is enabled only when the intended commercial use is covered by written data permissions and the deployment is configured. These market references are evidence for comparison; they are not counted among the 13 oracle providers and do not enter oracle consensus.
The reviewed Uniswap V3 WMON/USDC market on Monad contributes block-pinned spot and 15-minute TWAP observations, in-range liquidity, and Quoter V2 execution quotes at fixed MON sizes. Finalized Swap events are indexed separately for rolling source-local volume, and the API reports a warming state until 24 hours of contiguous coverage exists. This is execution and manipulation-context evidence, not an oracle provider and never an oracle-consensus vote.
Every on-chain feed includes contract addresses and explorer links so you can verify the source directly. API feeds are labeled as API Verified and include the source display name.
Robinhood Stock Token metadata, trading state, corporate actions, and multiplier data are exposed separately as first-party issuer context. Robinhood is not added to the provider count, consensus quorum, independence groups, or provider reputation.
Integration guides, code examples, and answers to common questions.
No account, no API key: pay per call in USDC on configured Base or optional Solana x402 networks. MPP remains available on EVM. Copy-paste quickstarts for REST and MCP.
Programmatic access to oracle prices, history, and batch queries with API keys.
Add two-sided pre-trade gates, Oracle Watch halt handling, and verified execution receipts to a DeFi agent.
Verify pre-trade and execution receipts locally — published on npm as verify-insight-receipt (v0.5.0). No API key, database access, or dependency on Insight being online.
Connect AI agents like Claude and Cursor via the Model Context Protocol — with pre-trade oracle safety checks and the always-on Oracle Watch signal.
View data fetching and analysis examples in JavaScript and TypeScript.
Common developer questions about symbols, providers, and historical data.
We support 13 oracle providers: chainlink, pyth, stork, chronicle, api3, redstone, dia, winklink, supra, twap, reflector, flare, and band. Pyth, Stork, Chronicle, and Supra DORA Push are direct Monad reads with source-timestamp freshness gates; Stork, Chronicle, and Supra remain observation-only until their source-overlap reviews are complete. Band uses the v3 Concurrent Price Stream and exposes its source timestamp to the same freshness and coverage checks used across Insight.
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.
The verifier is published on npm as verify-insight-receipt (v0.5.0): run npm install verify-insight-receipt, then call verifyReceipt(), verifyExecutionReceipt(), or verifyExecutionPair(). It recomputes the EIP-712 hashes and recovers signers locally without an API key, database access, or network request. Pass the published oracle-keys.json document separately when you also want key-window status. You can also install directly from the repository verifier/ directory.