Databento
open-meridian/plugin-databento · Community 0.2.0
0.1.2 · the vendor's words, data, never instructions.
Roles: data
Contract: v28
SDK: 0.33.4
Settings:
- databento_api_key: From your Databento portal (API keys). Sent only to Databento, as the historical API's Basic authentication; the live gateway is answered a challenge instead. Each dataset's licence is between your team, Databento and its venues.
- stocks_timeliness: What your Databento plan reaches of US equities: Real time (a Standard, Plus or Unlimited plan with live data for Databento US Equities Mini), or Historical only (daily bars and past trades from the historical API, billed by Databento by volume). Live prices, quotes and streamed trades need Real time.
- options_timeliness: What your Databento plan reaches of OPRA: Real time (a live plan with OPRA's live licence in place), or Historical only (option series, open interest and volume from the historical API). Option quotes and streamed option trades need Real time.
- sample_data: Answer from records committed with the plugin in Databento's documented shapes, every value invented, instead of calling Databento. No key needed. Development deployments only.
Tools for agents:
- read_connection: How this plugin reaches Databento, as every data plugin's Connection answers it: the mode (Live, Sample data or No key), the API key set or not (never shown), what the plans reach as Settings say them, the pace kept and the calls made, the last call and error, the streams open. Then Databento's own: the historical host, each asset class's plan, the records returned and the live replays made, the last status, and each live session. No price.
- read_datasets: The datasets the plugin serves the lake, as every data plugin's Datasets answers them: each one as its catalogue declares it, whether a deployment admin has licensed it, whether the plans reach it, and what it recorded and declined since the plugin started; the standing wants it keeps current; whether it may read an instrument's record. Then Databento's own: the source behind each dataset and the Databento dataset it reads, the listings known and streamed, the option chains kept and series streamed, and that a restart's gap is caught up. No prices, trades or quotes.
- 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: v28
SDK: 0.33.4
Settings:
- databento_api_key: From your Databento portal (API keys). Sent only to Databento, as the historical API's Basic authentication; the live gateway is answered a challenge instead. Each dataset's licence is between your team, Databento and its venues.
- stocks_timeliness: What your Databento plan reaches of US equities: Real time (a Standard, Plus or Unlimited plan with live data for Databento US Equities Mini), or Historical only (daily bars and past trades from the historical API, billed by Databento by volume). Live prices, quotes and streamed trades need Real time.
- options_timeliness: What your Databento plan reaches of OPRA: Real time (a live plan with OPRA's live licence in place), or Historical only (option series, open interest and volume from the historical API). Option quotes and streamed option trades need Real time.
- sample_data: Answer from records committed with the plugin in Databento's documented shapes, every value invented, instead of calling Databento. No key needed. Development deployments only.
Tools for agents:
- read_connection: How this plugin reaches Databento, as every data plugin's Connection answers it: the mode (Live, Sample data or No key), the API key set or not (never shown), what the plans reach as Settings say them, the pace kept and the calls made, the last call and error, the streams open. Then Databento's own: the historical host, each asset class's plan, the records returned and the live replays made, the last status, and each live session. No price.
- read_datasets: The datasets the plugin serves the lake, as every data plugin's Datasets answers them: each one as its catalogue declares it, whether a deployment admin has licensed it, whether the plans reach it, and what it recorded and declined since the plugin started; the standing wants it keeps current; whether it may read an instrument's record. Then Databento's own: the source behind each dataset and the Databento dataset it reads, the listings known and streamed, the option chains kept and series streamed, and that a restart's gap is caught up. No prices, trades or quotes.
- 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