TW Market Data LogoTW Market Data

Facts & statistics

Market facts

Long-run statistics for Taiwan equities, each with its sample period and as_of

Seasonality

Monthly return distributions and hit rates, with sample sizes

Institutional flow

Seasonality in the breadth of institutional net buying

Limit events

How often limit moves happen, and how concentrated they are

Delisting

Delisting counts and survival spans — the basis for avoiding survivorship bias

Rule changes

A timeline of trading-rule changes — the premise for reading historical data

Data & exploration

Dataset catalogue

Every dataset, its coverage, and how often it updates

Playground

Call the API from the browser, without a key

Market today

Today's market at a glance

Stock analysis

The entry point for looking at one instrument

Market heat map

The whole market in one picture — area is market cap, colour is revenue growth

Market calendar

Statutory disclosure deadlines — the day a figure may legally first be known

Platform capabilities

Product overview

What TWMD provides, and who it is built for

Verifiable proof

Signed checkpoints and per-row inclusion proofs

Data quality

Reconciliation, gap handling, and quality status

Methodology

How the figures are computed, and on what basis

Auditable execution

Tie a trading decision back to the data it saw

Connect your broker

Bring TWMD into an existing order and research workflow

Developers

Documentation

API reference, dataset pages, and integration guides

Quick start

Authentication and your first request

Integrate by role

Separate paths for quant research, data engineering, and app development

Connect over MCP

Point an agent straight at TWMD

MCP registry

The published MCP tool list and its signed manifest

Webhooks

Have your system told when data updates

Learn

Blog

Long-form writing on data, method, and market structure

Answers

Specific answers to specific questions, with sources

Topics

Industry chains and thematic relationships

Help centre

Account, billing, and usage questions

Glossary

Definitions for Taiwan-market and data terms

Compare & status

Why TWMD

A point-by-point comparison with FinMind and TEJ

Migrate from FinMind

Field mapping and migration steps

Migrate from FinLab

Field mapping and migration steps

Migrate from TEJ

Field mapping and migration steps

Status

Service availability and incident history

Security & trust

Trust centre

What we claim, and the limits on each claim

Security

Architecture, access control, and incident handling

Security facts

The items you can verify from outside

Security evidence

SBOM, ASVS mapping and threat model — including the three controls we do not meet.

Self-assessment

Item-by-item answers for a procurement questionnaire

Compliance & standards

Compliance mapping

Evidence primitives mapped onto FSB, IOSCO, and SR 26-2

Standards & interop

Term-by-term mapping onto published standards, and where it does not map

Provenance & C2PA

A machine-readable origin graph, fetchable without a key

Licensing

How the data may be used and redistributed

Adoption

Evaluate

Seven checks you can run yourself, without an account

Talk to sales

Enterprise plans, quotas, and contract detail

Pricing
中文Sign inSign up
TW Market Data

Taiwan market-data infrastructure, built for AI agents and quantitative workflows.

Status unknown
© 2026 TW Market Data

TW Market Data (TWMD) provides historical data and statistics, not investment advice; investment decisions and their risks are your own.

  • Privacy Policy·
  • Terms of Service·
  • Cookie Policy·
  • Acceptable Use Policy·
  • Data Sources & Licensing·
  • Legal (all documents)
中文

AI Agent

  • MCP Server
  • Skills
  • Tool manifest
  • Agent workflow examples
  • Agent benchmark
  • llms.txt
  • OpenAPI spec

Security

  • Security overview
  • Verifiable data
  • Trust Center
  • Standards & Interop
  • Regulatory mapping

Product

  • Datasets
  • Topics
  • Market facts
  • Documentation
  • Integration runbooks
  • Playground (no signup)
  • Free tier
  • Solutions

Company

  • About TWMD
  • Blog
  • Help centre
  • Pricing

Documentation

DASHBOARD

DashboardPricing

FOR AI AGENTS

MCP ServerSkillsllms.txtTool manifestOpenAPI SpecAgent workflow examples

OVERVIEW

OverviewQuick startAuthenticationSource policyData gradesData lineageMarket coverage

DATA APIS

GUIDES

How to get the 3 financial statementsHow to read institutional flowsHow to check market statusHow to wire a strategy / AI agent

SDKS

Release statusPython SDKJavaScript / TypeScript SDK

Building an AI agent? Start with /llms.txt for the full site index.

Overview

Coverage / Freshness

How far each data family reaches, how often it updates, and how to read the data_gaps signal.

Where the documentation starts

The left-hand navigation lists every dataset page, and Quick Start walks through building a first request.

For agents and internal tools that need to read the documentation programmatically, TW Market Data publishes /openapi.json, /llms.txt and /llms-full.txt as machine-readable entry points, and an MCP server at https://mcp.twmarketdata.com/mcp.

What coverage means

Coverage is the range a dataset actually spans — across tickers, dates, reporting periods or event types. It moves as sources publish and as datasets are productised, so no dataset should be assumed complete.

Treat coverage as an observable state rather than a constant. The API response and the dataset's own documentation are what govern, not an assumption made once at integration time.

  • TWSE daily prices: a core dataset, with coverage and data quality actively maintained.
  • Monthly revenue, income statement, balance sheet: updated on the cadence at which companies file and report.
  • Institutional net buy/sell: coverage is still being filled in — read it alongside data_gaps.
  • Technical indicators: derived from price data, so coverage follows whatever the underlying prices cover.
  • Cash flow statements, News Intelligence and similar topics: read the available/preview/deferred status on the docs page rather than assuming the dataset is fully live.

What freshness means

Freshness is the last time a given row was updated and available. Cadences differ by dataset: daily prices, monthly revenue, quarterly statements and event data are not published on the same rhythm.

When a query spans several datasets, check freshness together with each dataset's own time columns. Data that arrived on different cadences is not data from the same moment.

How to read data gaps

data_gaps marks a hole in the data or a limitation at the source. It is a signal worth keeping in a research pipeline, not a zero and not something to fill in automatically.

Carry data_gaps, source_role and lineage through the pipeline together, so a result can be audited and traced back later.

  • Establish whether the data exists before running numerical analysis or strategy logic over it.
  • A gap caused by a delay at the official source should be marked unavailable or pending, never filled with a substitute value.
  • When combining datasets, analyse on the intersection of available dates and record which gaps were excluded.

Dataset status categories

These are the status terms the platform uses, so that availability and its limits can be told apart inside your own systems.

  • available: part of the main public capability, still subject to your plan's access rights.
  • preview: usable for testing or specific scenarios; fields and coverage may still change.
  • coverage-limited: queryable, but the range is still being filled in.
  • deferred / not-yet-available: not yet part of the formal public capability.

Status by data family

  • Market prices: TWSE and TPEx daily prices are the primary entry point; technical indicators are a derived layer.
  • Fundamentals: monthly revenue and the three financial statements follow the official disclosure calendar.
  • Capital flow: institutional-flow is still going through productization rollout.
  • News Intelligence: metadata-first. It is not a commercial redistribution service for full news text.
  • Cash flow and other extended topics: the status note on the docs page governs; do not assume production-ready.

Reading coverage and freshness from the API and docs

Read the freshness, source_role, lineage and data_gaps fields on the response, then check them against the endpoint's own documentation and its parameter limits.

The dataset index (/datasets) and the individual dataset pages — /datasets/twse-daily-price, /datasets/institutional-flow — carry the same facts in longer form.

  • /docs/data-provenance
  • /datasets
  • /datasets/twse-daily-price
  • /datasets/monthly-revenue
  • /datasets/institutional-flow

Feedback

For a specific industry, a dataset that is not listed, or an enterprise deployment, get in touch.

On this page

  • Where the documentation starts
  • What coverage means
  • What freshness means
  • How to read data gaps
  • Dataset status categories
  • Status by data family
  • Reading coverage and freshness from the API and docs
  • Feedback