Documentation
Four roles evaluate a market-data vendor and each needs a different question answered. These are written per role, and every step says which surface carries it — REST, MCP, a file — and whether it works today.
Every step marked as working was probed against the live API on 2026-08-21. Steps that are not built say what is missing, and steps behind an entitlement a public probe cannot reach are marked as exactly that rather than being claimed.
A quant or researcher working in Python and a backtesting framework.
Get TWMD into your research environment without letting a backtest see the future.
4 of 6 steps work today
The data engineering team running Snowflake, Databricks or an EDW.
Treat TWMD as an upstream source with lineage, documentation and verifiability.
2 of 6 steps work today
Teams building financial agents on LangChain, a home-grown gateway, or an enterprise agent platform.
Make every number an agent uses traceable and checkable — and make it say so when it does not know.
4 of 6 steps work today
Second-line functions answering to SR 26-2, the EU AI Act, or internal model governance.
Be able to say what data the AI used, with evidence that does not rest on trusting the vendor.
4 of 6 steps work today
For how the proofs map onto published standards, see Standards & Interop.
