Data Sources & Freshness
Public overview of external data sources, refresh windows, and freshness behavior.
Solenvus combines live protocol data with cached platform responses.
This keeps the product responsive while preserving useful real-time context.
Main data sources
Used for Solana network health signals such as:
Used for SOL price data such as:
Jupiter Quote API v6
Used for live quote paths during supported execution flows.
Helius Enhanced Transactions API
Used for real on-chain event ingestion in platform activity views.
Freshness windows
The platform uses these cache intervals in the current implementation:
Network health: 12 seconds
Activity polling for real events: 60 seconds
Protocol status page refresh: 30 seconds
What freshness means for users
Fresh data helps users understand current execution conditions.
It is especially useful before running live or hybrid skill executions.
Stale fallback behavior
If a live upstream source is temporarily unavailable, the platform can return the last known cached value.
Where supported, stale state is exposed clearly so users can judge current reliability.
