Ordinary market history comes from two providers, and every ordinary ticker can pin its own:
- Yahoo Finance (via the bundled Python sidecar): the broadest fund coverage, and the source for profile/metadata, including a fund's category and expense ratio, a stock's sector and core stats alike. Its feed is unofficial and intended for personal use, so in the commercial edition it is off until you opt in.
- Tiingo: a documented API with a free key, the recommended default. The key is stored locally on your machine, never in the database or its backups.
Namespaced TSP:* funds use the official TSP CSV lane instead of either market
provider. Cash-like local rows and Treasury-curve data are also source-specific;
none of those symbols is sent to Yahoo as a fallback. Securities & prices therefore
hides Yahoo profile fetch for TSP:*, locks its source and download-enabled state,
and repairs stale metadata when saved. The main-process provider boundary rejects
the namespace too, so a stale screen or crafted request still cannot reach Yahoo
or Tiingo.
The TSP update prices the TSP:* funds you have added and adds no others: a
fund joins only when you add it (Settings' Add TSP funds, or the picker when
you enter a statement), so a fund you delete stays deleted. Once a fund is
added, its name, category and expense ratio are yours to edit, and an update
never writes over them; only a placeholder row (a fund typed on a statement
before it was ever added) takes the catalog's details. tsp.gov publishes one file
with every fund's whole history, and the update writes only the prices that
differ from the ones stored, so an update on a day tsp.gov published nothing new
writes nothing, counts no fund as updated and starts no Screener rebuild. A fund
the file no longer lists (a retired or renamed fund, or a symbol the catalog
does not know) is named as not updated, and its stored history is kept.
Tickers without a pin follow the global default on Settings; a per-ticker override exists because each source has tickers the other covers badly. Turning Yahoo on with no Tiingo key saved, whether in first-run setup or in Settings, also makes Yahoo the default; otherwise every download would still wait on a key you haven't added. In first-run setup the rule also runs the other way: unticking Yahoo there while a Tiingo key is already saved flips the default to Tiingo, so the wizard never finishes with the default pointed at the source you just turned off. In Settings you change the default yourself.
Tiingo's hourly limit
Tiingo's free plan allows 50 requests an hour, and a price update asks once for each fund that uses Tiingo. When Tiingo answers that the hour's requests are used up, the update stops asking it and says how many funds are waiting for Tiingo's hourly limit. Those funds are not failures: their stored prices are unchanged, and the next update asks for them first, since it always starts with the funds whose prices are oldest. A paid Tiingo plan has a higher limit, and the app simply keeps asking until Tiingo says stop.
The wizard's Price data step
A commercial-edition guided setup asks this right after About you, before any account exists. It presents the same Yahoo checkbox and an inline Tiingo key field, no separate Save. Continue stays disabled until the resolved configuration can actually fetch, naming the reason inline when it can't. Landing on a Tiingo default runs a live key check first. A saved-but-revoked key fails here instead of failing silently later, once per ticker. Skip for now writes nothing at all, including a ticked Yahoo box: the install leaves with whatever was already saved, unchanged, and you can finish the setup later in Settings → Price data.
"Set up price data"
A new commercial install has neither feed ready: Tiingo is the default but has no key yet, and Yahoo is off until you opt in. Until one of them works, the top bar's Update Prices button becomes Set up price data and takes you to Settings → Price data, where a notice names what's missing. This is deliberate. Running a download in that state fails once per ticker rather than telling you the one thing that's wrong.
The exception is a portfolio whose held holdings that need a download are all TSP funds. The tsp.gov lane needs neither Tiingo nor Yahoo, so Update Prices (and the Overview's Rebuild history) runs there, for the TSP funds and any cash-like holdings only; it never asks a price source about funds you do not hold. Holding any other fund that downloads asks for a feed again.
Two ways out, either is enough: paste a Tiingo key (their free tier covers a personal portfolio), or tick Enable Yahoo Finance.
On the Screener, tickers without a usable trailing-return period are excluded from rankings while working results remain. The compact summary gives the excluded count and links to this same Update/Setup action; a full recovery message appears only when the current comparison has no usable result.
Recovery from an empty history
The Overview's empty value chart evaluates the whole-library price setup: it offers a rebuild only when the default route is usable, otherwise it opens the specific Price data or License prerequisite.
Securities & prices evaluates one ticker more precisely. A ticker pin takes precedence over the default; cash-like local history and the official TSP feed do not require a market provider; Skip DL routes to the ticker editor; Tiingo without a key routes to Tiingo setup; and Yahoo without personal-use consent routes to the Yahoo consent control. An expired commercial trial routes to License before any of those write actions. These recovery paths never change a source, grant consent, or download more than the action names.
Why downloads are slow on purpose
Yahoo has two lanes, paced differently on purpose.
Profile and metadata fetches run strictly one at a time. Measured against a few thousand real tickers, any concurrency above one trips Yahoo's per-IP rate limiting (HTTP 429) somewhere past roughly 600 requests, and the backoff that follows makes the whole job slower than never having hurried. Going faster was the thing making it slow. That's why a bulk profile fetch shows a steady ticker-by-ticker progress line rather than finishing in one burst.
Price history is fetched in batches of about 25 tickers, downloaded together. The batch size is the progress cadence, not a throttle. It is still a lot of requests: a full rebuild over a thousand-ticker universe takes minutes and can still brush a limit.
Before Yahoo prices are saved for a fund you hold, the update asks Yahoo which splits it has had. Prices saved across a split the app doesn't know about would put the earlier days at the split ratio times their worth. So if Yahoo answers that one fund's split check failed, which happens when it is limiting requests, an ordinary update leaves that fund's prices as they were and lists it as failed (unless Yahoo has no prices for it at all, as for a fund that no longer trades); the next update asks for them again. In every other case the prices are saved and the status line notes the funds updated without a split check: a rebuild, a fund with no downloaded history yet, or a split request that failed as a whole (a timeout). If a split does turn up later, the update downloads that fund's stored history again in the same step, so it all ends up on one basis.
A fund whose only stored price is one you typed (a statement price entered in account setup or with a holdings snapshot) has no downloaded history yet. Its next update downloads the whole history and keeps the price you typed.
Failures are recoverable: a bulk download reports which tickers failed and can retry just those. If one ticker's history is persistently wrong at one source, pin it to the other. If a split looks missing, see manual splits rather than re-downloading in a loop.