Tiingo
open-meridian/tiingo · Community 0.9.0
0.9.0 · the vendor's words, data, never instructions.
Roles: data
Contract: v29
SDK: 0.35.2
Settings:
- tiingo_api_token: From your Tiingo account's API page. Tiingo's free plan suffices for a few funds' daily NAVs; its terms are for your internal and personal use.
- openfigi_api_key: Optional: your OpenFIGI API key, from your OpenFIGI account. Each fund's ticker is mapped to its FIGIs through OpenFIGI so it meets the platform's record; without a key, at OpenFIGI's lower keyless limits.
- funds: The mutual funds to keep daily net asset values for.
- sample_data: Answer from built-in made-up data instead of the source, changing nothing else the plugin does. Development deployments only.
Tools for agents:
- read_connection: How this plugin reaches Tiingo, as every data plugin's Connection answers it: the mode (Live, Sample data or No key), the API token set or not (never shown), what Tiingo serves the token, the free plan's limits it keeps and its requests, the last check and error; it does not stream. Then Tiingo's own: the source, the requests this hour and today, and how many responses are kept. No price.
- read_datasets: What this plugin serves the lake, as every data plugin's Datasets answers it: its one dataset as the catalogue declares it (mutual funds' daily NAVs, New York's day ending at 16:00, one person's terms), whether a deployment admin has licensed it, what it recorded and declined; the standing wants it keeps current and the wants it answered; whether it may read an instrument's record. Then Tiingo's own: each fund listed with what Tiingo says it is, whether it is served, the deployment's record for it or why there is none, up to 100. No NAV.
- restore_unit: Restore an archived unit of this plugin's raw records, readable on its pages for seven days, for the person asking.
Interface: pages it draws
Contract: v29
SDK: 0.35.2
Settings:
- tiingo_api_token: From your Tiingo account's API page. Tiingo's free plan suffices for a few funds' daily NAVs; its terms are for your internal and personal use.
- openfigi_api_key: Optional: your OpenFIGI API key, from your OpenFIGI account. Each fund's ticker is mapped to its FIGIs through OpenFIGI so it meets the platform's record; without a key, at OpenFIGI's lower keyless limits.
- funds: The mutual funds to keep daily net asset values for.
- sample_data: Answer from built-in made-up data instead of the source, changing nothing else the plugin does. Development deployments only.
Tools for agents:
- read_connection: How this plugin reaches Tiingo, as every data plugin's Connection answers it: the mode (Live, Sample data or No key), the API token set or not (never shown), what Tiingo serves the token, the free plan's limits it keeps and its requests, the last check and error; it does not stream. Then Tiingo's own: the source, the requests this hour and today, and how many responses are kept. No price.
- read_datasets: What this plugin serves the lake, as every data plugin's Datasets answers it: its one dataset as the catalogue declares it (mutual funds' daily NAVs, New York's day ending at 16:00, one person's terms), whether a deployment admin has licensed it, what it recorded and declined; the standing wants it keeps current and the wants it answered; whether it may read an instrument's record. Then Tiingo's own: each fund listed with what Tiingo says it is, whether it is served, the deployment's record for it or why there is none, up to 100. No NAV.
- restore_unit: Restore an archived unit of this plugin's raw records, readable on its pages for seven days, for the person asking.
Interface: pages it draws