Market Data Status
Review whether the portal is using live Finnhub data, mock educational data, stale cached data, provider fallback, or unavailable data states.
Function availability
Finnhub live data metrics
When Finnhub is the active provider and FINNHUB_API_KEY is set server-side, real market data flows through the serverless proxy. The metrics below update on each diagnostics refresh.
Run diagnostics to see live provider metrics. Static mode uses mock educational data.
Health checks, latency, fallback, and cache simulation
The health endpoint checks provider configuration and fallback readiness without calling real paid APIs or exposing secret values.
Checking provider health
Diagnostics will appear here when Netlify Functions are available. Static mode remains supported with mock educational data.
Current provider implementations
To activate Finnhub: set FINNHUB_API_KEY and MARKET_DATA_PROVIDER=finnhub in Netlify environment variables. The frontend never sees these keys.
Finnhub free tier limits and caching strategy
The in-memory serverless cache prevents duplicate Finnhub calls for the same symbol within a 55-second window across warm function instances. On rate limit (HTTP 429), the function returns safe mock fallback data with a user-facing warning.
API keys are never placed in frontend JavaScript
Real provider keys must be configured only as Netlify or serverless environment variables. If no provider is configured, the portal uses mock educational data or safe fallback data.
This analysis is for educational and informational purposes only and does not constitute financial advice.