Compare
Moving from TEJ to TW Market Data
This is a change of procurement model as much as of API. TEJ's site does not publish prices and directs enquiries to its sales and consultation pages; here you self-serve with a card and can start without talking to anyone. The engineering work is mostly re-expressing a delivered extract as a query.
What maps to what
| TEJ | TW Market Data |
|---|---|
| A negotiated data package with an agreed field list | A published dataset catalogue you read before buying |
| Scheduled deliveries or a database extract | Queries on demand over HTTPS, plus an MCP interface for agents |
| Point-in-time handled inside your contracted extract | A knowledge date on every disclosure row, an as-of cutoff on the MCP interface, and a declared point-in-time status per dataset |
| Support through an account manager | Public documentation, a status page, and direct contact for vendor reviews |
When to stay with TEJ
- You need markets beyond Taiwan in one contract. TEJ's site describes coverage across Taiwan, China and Hong Kong; we are Taiwan-only and are not trying to be otherwise.
- Your institution requires a negotiated contract, an account manager, or terms we do not offer self-serve.
- You depend on datasets we do not publish. The catalogue is public precisely so this is answerable before anyone signs anything.
Questions
Is this a like-for-like replacement?
For Taiwan market data with point-in-time queries and traceable lineage, the capabilities overlap. For a multi-market institutional contract with negotiated terms, it is not, and we would rather say so here than discover it in an evaluation.
How do we evaluate before committing?
Read the dataset catalogue, run the free tier against a period you already hold data for, and compare value by value. Every response carries the upstream endpoint and table, so a mismatch is a traceable question rather than an opinion.
The four-way comparison table sets out the same ground with every factual cell cited to the vendor's own documentation.
Statements about TEJ on this page reflect its own published documentation, read on the date shown on the comparison page.