Hi! I’m reaching out from Qveris.ai.
Qveris provides a unified financial data API for market data, fundamentals, company data, macro data, and news. I noticed QuantDinger already separates market data ingestion from strategy/backtest/execution, and supports several optional data APIs. That seems like a good fit for an optional Qveris adapter that could reduce the number of separate provider keys users need to configure.
Would you be open to a PR that adds Qveris as an optional market data provider?
Possible scope:
- add
QVERIS_API_KEY / QVERIS_BASE_URL config
- implement a read-only market data adapter for the existing quote/OHLCV/fundamentals interfaces where applicable
- keep it disabled by default so existing behavior is unchanged
- add docs and a small example showing how to enable it
Happy to maintain the integration and provide test API credits for maintainers if useful. If there is a preferred adapter boundary or contribution path, I can follow that.
Hi! I’m reaching out from Qveris.ai.
Qveris provides a unified financial data API for market data, fundamentals, company data, macro data, and news. I noticed QuantDinger already separates market data ingestion from strategy/backtest/execution, and supports several optional data APIs. That seems like a good fit for an optional Qveris adapter that could reduce the number of separate provider keys users need to configure.
Would you be open to a PR that adds Qveris as an optional market data provider?
Possible scope:
QVERIS_API_KEY/QVERIS_BASE_URLconfigHappy to maintain the integration and provide test API credits for maintainers if useful. If there is a preferred adapter boundary or contribution path, I can follow that.