China’s Finance Giant Bets the Future of Market Data Is Agent-Native

The Hype Moment: When Market Data Became a Skill

The current surge in AI agent tooling has turned every SaaS product into a candidate for “MCP server” status. Financial data, however, presents a harder problem than todo lists or CRMs: provenance matters, latency matters, and a hallucinated earnings number is costlier than a misquoted restaurant review. Into this landscape, HiThink—known to Chinese investors as 同花顺, the dominant retail financial terminal—has open-sourced its official A-share data service with a framing that is deliberately agent-first. The repository does not merely expose REST endpoints; it ships a unified “Skill” meant to teach Claude, Cursor, and Windsurf how to query China’s equity markets without human developers acting as intermediaries. That shift in target audience—from programmer to LLM—is what triggered the attention spike.

What Pedigree Means in the A-Share Maze

China’s A-share market is notoriously idiosyncratic. It has limit-up and limit-down regimes, call-auction phases, “dragon and tiger” board disclosures of top buyers and sellers, and complex corporate action calendars that make naive backtests dangerous. Western data providers such as FMP, Finnhub, and Alpha Vantage cover global fundamentals well, but their China equity depth is typically shallow or delayed. AllTick and Infoway offer real-time A-share feeds and even Level-2 order books, yet they remain traditional API vendors: you get a key, read the docs, and write the integration.

HiThink’s entry is different because it is the source. As the incumbent retail broker and data terminal provider in China, it owns the data pipeline rather than scraping or licensing it secondhand. The repository’s coverage reflects that insider status: it includes not only standard snapshots and financial statements, but also China-specific microstructure datasets like the limit-up pool, broken-board stocks, consecutive-board ladders, and individual stock anomaly alerts. These are not exotic add-ons in Shanghai and Shenzhen; they are the daily vocabulary of retail traders. By publishing them through an official channel, HiThink is solving a provenance problem that plagues quantitative researchers who otherwise rely on patchwork scrapers.

A Monorepo with Many Doors

Technically, the project is structured as a monorepo that refuses to pick a single consumption model. It exposes a REST layer for existing systems, hosted MCP servers for chatbot integration, a Node.js CLI for terminal workflows, a Python toolkit for notebook research, and a local DuckDB instance—marketdb—for offline analytics. This is not feature bloat; it is an admission that agents and humans consume data at different cadences. An LLM answering a casual question about Kweichow Moutai’s valuation needs a lightweight MCP tool call. A quant preparing a multi-factor backtest needs years of adjusted daily bars dropped into a local columnar database so that SQL, not HTTP, becomes the query language.

The local-first option is particularly notable. The README explicitly warns that large, multi-symbol, or long-range results must be written to disk rather than returned into an agent’s conversation context. That constraint—context windows are expensive and slow—drives the design toward DuckDB as a staging layer. It is a pragmatic recognition that even the most advanced LLM is a poor substitute for a database when the payload is a decade of tickers. Infoway streams real-time candles over WebSocket; HiThink, by contrast, seems to accept that agents will often want to batch-download and query locally.

The CLI is worth a separate mention because it is built in Node.js and runs independently of the Python stack. That choice acknowledges the JavaScript ecosystem’s dominance in agent tooling—MCP servers are often TypeScript-native—while keeping Python for the quantitative heavy lifting. The result is a product that can run on a developer laptop without requiring a separate database server, yet still scale to full-market historical dumps.

The Skill Is the Interface

The most genuinely special piece of the repository is not any single endpoint, but the hithink-finance Skill. This is essentially a system prompt and contract mirror that lives in the repo under skills/hithink-finance/. It tells an agent how to disambiguate stock names into unique thscode identifiers, when to prefer remote APIs versus the local DuckDB, how to handle API keys without leaking them into generated code, and how to format financial analysis with mandatory “non-investment advice” disclaimers.

In other words, HiThink is not just publishing data; it is publishing an instruction manual for autonomous consumption. The Skill auto-routes tasks across the monorepo’s modalities: if the agent detects a Python environment, it may use the SDK; if it is running inside Claude Desktop, it may use the MCP server; if the result set is huge, it may invoke the CLI and return a file path. This meta-layer turns the repository from a data product into an agent capability. Alpha Vantage also advertises an MCP server, but HiThink’s Skill goes further by embedding governance rules—stock code disambiguation, source attribution, and refusal to simulate missing data—directly into the agent’s context.

That refusal to hallucinate is worth highlighting. The README contains an unusually blunt clause: when a capability is missing, the agent must state so clearly and must not use simulated or static examples as substitutes. In an era where vendors often demo with stale JSON placeholders, this is a welcome constraint. It also aligns with the broader guidance from QVeris that agents should verify feed provenance and quote validity before acting on a live price.

Honest Boundaries

For all its breadth, the repository is refreshingly explicit about its boundaries. Minute-level bars, tick data, overseas markets, macroeconomic series, and news or research report text are all listed as currently out of scope. That honesty saves integrators from nasty surprises. If you need sub-minute latency or Level-2 depth, Infoway or AllTick are more appropriate. If you need US equities, FMP or Finnhub remain the standard. HiThink’s offering is mid-to-low frequency A-share research infrastructure, not a high-frequency trading stack.

There are also operational rough edges visible in the sources. The project recently migrated to a monorepo layout, and the README includes a migration guide for users updating editable Python installs and script paths. That suggests the surface area is still shifting. The Node.js CLI is newer than the Python stack, and the “Skill” abstraction is novel enough that its durability across agent framework versions remains unproven.

Outlook: From Open Finance to Agent Finance

The broader context, as described in Plaid’s open finance framework, is that financial APIs are evolving from one-to-one partner integrations into many-to-many open ecosystems. HiThink’s repository accelerates that trend inside the AI agent niche. It treats the LLM not as a consumer of a dashboard, but as a first-class runtime that needs authenticated, governed, multi-modal access to structured data.

The unresolved tension is whether the “Skill” abstraction becomes a standard or a silo. If every data vendor publishes its own Skill format, agents will spend more time learning idiosyncratic toolkits than analyzing markets. HiThink’s bet is that by open-sourcing the Skill alongside the data contracts, it can establish itself as the default data layer for A-share agents before a cross-vendor standard solidifies. Given the size of China’s retail market and the relative scarcity of official, agent-ready domestic data, that is not an unreasonable wager. The real test will be whether the Skill’s auto-routing logic survives the next wave of agent framework updates—and whether quants trust an LLM-mediated data layer with real capital.