CN/HK Financial Report Facts Index avatar

CN/HK Financial Report Facts Index

Pricing

from $7.00 / 1,000 results

Go to Apify Store
CN/HK Financial Report Facts Index

CN/HK Financial Report Facts Index

CN/HK financial report facts index for A-share and HK; supports scan and section retrieval with 2023-2025 historical reports and 2026+ daily incremental updates.

Pricing

from $7.00 / 1,000 results

Rating

0.0

(0)

Developer

dianming hu

dianming hu

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

CN/HK Financial Report Facts Index (2023-2025 + 2026+ Incremental)

This Actor is an Apify bridge to cube-mcp financial-report facts for China A-shares (CN) and Hong Kong stocks (HK).

What this Actor does

  • Supports semantic scan (scan) and full section retrieval (section) for CN/HK filings.
  • Historical coverage: annual, semi-annual and quarterly data for 2023–2025.
  • Incremental updates: from 2026 onward, synchronized daily.
  • Best suited for Agent workflows: MCP/LLM callers can consume concise evidence rows with source traceability.

Authentication model

The actor uses the Apify secret cube_mcp_key mapped as MCP_API_KEY in .actor/actor.json.

Users run the actor with normal business inputs only; they do not provide cuecue/MCP credentials directly.

Input

Common fields

  • market (required): one of cn, hk, both (default cn).
    • both runs both markets and merges results.
  • mode (required): one of scan, section (default scan).
  • period (optional): report period as string (default 2025).
  • outputLanguage (optional): en (default, Agent-friendly) or zh.
    • en returns translated/normalized summary/resultText/sectionTitle.
    • Chinese originals are preserved in summaryZh, resultTextZh, sectionTitleZh.

Scan mode (mode: "scan")

  • query (string, optional; required if no anchor)
  • anchor (string, optional; required if no query)
  • defaultSectionKey (optional): fallback section key when anchors are not provided (default financial_report)
  • limit (optional, integer): 1..30, default 15
  • autoSection (optional, boolean): if true, auto-fetch section content for top scan rows
  • autoSectionLimit (optional, integer): 1..5
  • focus (optional): default (keep all) or investment (filter/rank by investment keywords)
  • focusKeywords (optional, comma/semicolon/newline separated string)
  • focusKeywordMinMatch (optional, integer): minimum keyword matches in investment mode (default 1)
  • summaryMode (optional): true (default) keeps compact output; false includes raw section fields where available

Section mode (mode: "section")

  • stockCode (required): stock code, e.g. 300098
  • sectionKey (required): section key, e.g. financial_report
  • period (optional): report period, default 2025
  • docKey (optional): optional direct doc targeting
  • nodeId (optional): optional direct node targeting
  • summaryMode (optional): default true

Output

Scan result fields (default)

Main fields:

  • market, mode, tool, period, query, anchor
  • company, doc_key, node_id
  • summary, resultText, sectionTitle
  • score
  • source: pdf_url, publish_date, doc_id
  • focusMode, focusMatchCount, focusMatchedKeywords, focusScore

Trace fields:

  • summaryZh, resultTextZh, sectionTitleZh

No separate ...En duplicate fields are emitted in this actor.

Section result fields

  • stockCode, sectionKey, period
  • summary, resultText, source
  • summaryZh, resultTextZh

Example inputs

{
"market": "cn",
"mode": "scan",
"query": "营收",
"period": "2025",
"limit": 10,
"focus": "investment",
"focusKeywordMinMatch": 1,
"outputLanguage": "en"
}

2) Section retrieval

{
"market": "cn",
"mode": "section",
"stockCode": "300098",
"period": "2025",
"sectionKey": "financial_report",
"docKey": "cn_fr:300098:2025:annual_report",
"nodeId": "n0005",
"summaryMode": false
}

3) Scan with auto section

{
"market": "cn",
"mode": "scan",
"query": "营收",
"period": "2025",
"limit": 10,
"autoSection": true,
"autoSectionLimit": 2,
"outputLanguage": "en"
}

Output example

{
"market": "cn",
"mode": "scan",
"tool": "scan_financial_report_evidence",
"period": "2025",
"query": "营收",
"company": "300098",
"doc_key": "cn_fr:300098:2025:annual_report",
"node_id": "n0005",
"sectionTitle": "1.1 Automotive Electronics",
"summary": "In this section, the company operating revenue reached 857,566,178.58 CNY...",
"resultText": "In this section, the company operating revenue reached 857,566,178.58 CNY...",
"summaryZh": "在本章中,公司营业收入达到857,566,178.58元...",
"resultTextZh": "在本章中,公司营业收入达到857,566,178.58元...",
"sectionTitleZh": "1.1 汽车车载产品",
"source": {
"pdf_url": "http://static.cninfo.com.cn/finalpage/2026-04-18/1225118884.PDF",
"publish_date": "2026-04-18",
"doc_id": "1225118884"
},
"score": 0.81714
}

API call (minimal)

curl -X POST "https://api.apify.com/v2/acts/<YOUR_ACTOR_ID>/runs?token=<APIFY_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"input": {
"market": "cn",
"mode": "scan",
"query": "营收",
"period": "2025",
"limit": 5,
"outputLanguage": "en"
}
}'

FAQ

Q: Do users need to enter a cuecue/MCP key?
A: No. End users use only actor inputs. The platform secret is configured by the actor owner as MCP_API_KEY.

Q: How should an Agent consume output?
A: Use summary, resultText, and sectionTitle as primary fields. Keep *Zh fields (summaryZh, resultTextZh, sectionTitleZh) for traceability.

Q: Why might scan return fewer/no rows?
A: Check focus="investment" and focusKeywords settings. If enabled, rows not matching enough investment keywords are filtered.