Guotai Haitong Lingxi Market Ranklist Query

Problem

In market-data conversations, models can confuse the volume ranklist with the amount ranklist, force unsupported dimensions into the answer, or trim middle rows with ellipses. This skill constrains Guotai Haitong Lingxi market ranklist queries to a fixed parameter surface: ranklist, code, limit, offset, order_by, sorted_type, and mask, reducing field drift.

How It Works

• Authorization first: before returning market data, it checks for gtht-entry.json; if missing, the flow obtains or refreshes an API Key via QR code or API Key.
• Only mapped dimensions: order_by covers latest price, price change, percentage change, amplitude, five-minute speed, turnover rate, market cap, P/E, volume ratio, volume, amount, and daily net inflow. In particular, 9 is volume, 10 is amount, and 11 is net inflow; these are not interchangeable.
• Fixed A-share scope: requests resolve to code=BK101003. Board-specific or sector-specific ranklist requests fall back to the default scope and the response identifies the result as an A-share ranklist.
• Complete output: when the user asks for top N, bottom N, or all rows, it lists the returned rows without replacing middle entries with ellipses.

Boundaries

It is suitable for A-share market ranklists and sorted results, not for deep fundamentals, announcement interpretation, full news articles, or other non-ranklist tasks. If the request exceeds the supported parameter model, it should stop inferring and direct the user to the Guotai Haitong Lingxi app.