Stop maintaining vendor connectors.
QuantJourney maintains the integration layer your applications and agents depend on: authentication, provider-specific requests, failure handling, stable contracts and source metadata. This catalog shows a representative, commercially useful set—not a dump of every method in the codebase.
Approved sources behind one governed contract.
Access requirements describe how the provider is typically reached. Always rely on your own agreement and the provider's current terms.
| Integration | Workflow | Access | Credential | Provider |
|---|---|---|---|---|
| Official and public sources | ||||
| FREDEconomic series, releases and observations | Macro research | Public sourceNo paid QJ data entitlement | None / provider policy | Provider ↗Official terms ↗ |
| SEC EDGARFilings, issuer facts and regulatory evidence | Issuer diligence | Public sourceSubject to SEC fair-access policy | None | Provider ↗Official terms ↗ |
| CFTCCommitments of Traders and positioning data | Futures positioning | Public sourceOfficial U.S. regulator data | None | Provider ↗Official terms ↗ |
| Deutsche BundesbankOfficial German monetary and financial series | European macro | Public sourceOfficial SDMX / time-series service | None | Provider ↗Official terms ↗ |
| European Central BankRates, FX and monetary-policy series | European macro | Public sourceOfficial ECB data services | None | Provider ↗Official terms ↗ |
| OECDCross-country economic indicators | Global macro | Public sourceProvider terms apply | None | Provider ↗Official terms ↗ |
| World BankDevelopment and country indicators | Global macro | Public sourceDataset-specific terms may apply | None | Provider ↗Official terms ↗ |
| Commercial market-data accounts | ||||
| Financial Modeling PrepMarket data, fundamentals and company information | Equity research | Commercial accountSubscription remains in your name | API key | Provider ↗Official terms ↗ |
| EOD Historical DataPrices, fundamentals and corporate actions | Equity research | Commercial accountSubscription remains in your name | API token | Provider ↗Official terms ↗ |
| Twelve DataMulti-asset prices, reference data and indicators | Market data | Provider accountPlan and data rights come from Twelve Data | API key | Provider ↗Official terms ↗ |
| DatabentoInstitutional historical and live market data | Market data infrastructure | Commercial accountDataset entitlements remain with Databento | API key | Provider ↗Official terms ↗ |
| Exchange and reference access | ||||
| CboeExchange market statistics and approved datasets | Options and volatility | Exchange termsAvailability follows the customer's Cboe rights | As required by dataset | Provider ↗Official terms ↗ |
| OpenFIGIFinancial-instrument identifier mapping | Reference data | Provider accountOpenFIGI limits and terms apply | API key | Provider ↗Official terms ↗ |
| Digital assets and DeFi | ||||
| Morpho BlueLending markets, supply, borrow and utilization | DeFi credit | Public protocol dataEndpoint and protocol terms apply | None for public data | Provider ↗Official terms ↗ |
| DefiLlamaProtocol TVL, liquidity and market context | DeFi research | Public APIProvider policy applies | None for public API | Provider ↗Official terms ↗ |
| CoinGeckoDigital-asset prices and market reference data | Crypto research | Provider accountFree and paid provider plans exist | API key by plan | Provider ↗Official terms ↗ |
Deliberately omitted: raw method counts, generated docstrings, private exchange-account actions and summaries of redistribution rights. Those belong in technical or legal diligence, not sales copy.
What the registry means—and what it does not.
Is this the entire internal connector list?
No. This is the representative public view for buyers. The complete route, provider, entitlement and deployment matrix is reviewed during technical diligence.
Does QuantJourney resell the data?
No. You contract with the provider where an account or commercial license is required. QuantJourney licenses and maintains the software layer that governs access to those sources.
Why not publish every endpoint and method here?
A long generated method list is not evidence of a coherent product. Buyers need supported workflows, access requirements, operating boundaries and a stable governed contract. Detailed reference documentation remains available for implementation teams.
Can you connect an internal database?
Yes, as separately scoped professional services. Internal systems, custom schemas and data-lake integration are not implied by the standard Private Deployment subscription.