A-Share Dragon-Tiger List Market Data API

Problem

In A-share market analysis, strategy backtesting, and research workflows, the Dragon-Tiger List is often used to inspect unusual fund movement, seat behavior, and attention on individual stocks. Scraping pages or assembling fields by hand creates three issues: inconsistent data definitions, hard-to-validate missing fields, and unstable inputs for LLM or downstream scripts. @user_3391caa4/lhb-api aims to turn this A-share Dragon-Tiger List market data into an API-oriented interface, making it easier to fetch, normalize, and use in engineering workflows.

How It Works

This is a data-interface skill rather than an investment-analysis product. Its core job is to expose Dragon-Tiger List-related data as structured inputs for LLM workflows. A typical path looks like:

• define the data scope to query, such as stock, date, or board dimension;
• call the interface exposed by the skill;
• convert the response into explicit JSON fields for summarization, comparison, storage, or prompt templates;
• reuse the same field structure in scripts or Agent pipelines to reduce manual reshaping.

For engineers, the value is mainly in turning “find data, inspect fields, assemble structure” into a more stable interface, not in replacing market terminals, databases, or decision systems.

Boundaries

Based on the available material, treat it as an access and integration entry point for A-share Dragon-Tiger List market data. Field coverage, authentication, rate limits, data source, and update timing should be confirmed before integration. It should not be used directly for trade execution, compliance reporting, or published research conclusions without field validation and clear data definitions.