Price sources — Yahoo Finance & CoinGecko
Every price you see comes from Yahoo Finance (equities, ETFs, indices, FX) or CoinGecko (crypto — Yahoo also falls back here for a crypto pair it doesn’t carry). Both are always on, no toggle: the app depends on having a price source at all.
What leaves the machine
Only the ticker symbols (and, for crypto, coin ids) you’re asking about — never balances, holdings, position sizes, or anything else about your book. The provider sees “what’s AAPL/BTC worth right now,” never “what does this person own.”
API keys
| Provider | Key required |
|---|---|
| Yahoo Finance | None |
| CoinGecko | None — keyless at a modest rate limit; add a Demo/Pro key in its settings to raise it |
The app throttles itself conservatively either way, so a burst of chart views won’t get your key or IP rate-limited.
Caching
A live quote is cached ~1 minute; charts and historical series up to 30 minutes, depending on timeframe — switching tabs or refreshing reuses a recent answer instead of re-fetching. Separately, a background scan (~15 minutes by default, configurable in Intel’s monitoring settings) walks every holding and watched ticker on its own, independent of anyone looking at the app.
A note for the security-conscious
These calls always go to Yahoo’s and CoinGecko’s fixed hosts, never a URL you or Lucius supply — no way to point a lookup at an address of your choosing. This pair is a documented exception to the app’s hardened outbound fetch path (which pins a DNS resolution to one IP for the request’s life); it uses a plainer HTTP call instead. Flagged for transparency, not because a fixed-host market-data call exposes a practical way to reach anything internal.
Related pages
lucius/overview— asking about a price or holding directlyoperations/security-and-privacy— what else leaves this machine, and when