QCC — Company Announcements

Retrieve company announcements for a company identified by its full registered name or Unified Social Credit Code with the QCC API. Supply a search key. Sample fields include content and text. Use it for account research or company due diligence.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body* object
Company full registered name or Unified Social Credit Code.
Retrieve company announcements for a company identified by its full registered name or Unified Social Credit Code.

Sample response

"_meta": {
  "io.modelcontextprotocol/serverInfo": {
    "icons": [
      {
        "mimeType": "image/png",
        "sizes": [
          "60x60"
        ],
        "src": "https://qcc-static.qcc.com/resources/web/omaterial/favicon.png"
      }
    ],
    "name": "qcc-mcp",
    "title": "QCC MCP",
    "version": "1.0.0",
    "websiteUrl": "https://www.qcc.com/"
  }
}
content [1]
[0] {}
textJSON string · parsed preview
content[0].text
{
  "企业名称": "企查查科技股份有限公司",
  "摘要": "该查询实体共有14条企业公告记录。",
  "企业公告信息": [
    {
      "公告标题": "企查查科技股份有限公司发行上市审核进度公告",
      "公告类型": "首发",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2026-10-09"
    },
    {
      "公告标题": "关于终止对企查查科技股份有限公司首次公开发行股票并在沪市主板上市审核的决定",
      "公告类型": "首发",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2026-10-09"
    },
    {
      "公告标题": "企查查科技股份有限公司主板首次公开发行股票招股说明书(申报稿)",
      "公告类型": "招股说明书、首发",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2026-03-31"
    },
    {
      "公告标题": "8-1 发行人及中介机构关于首轮审核问询函的回复(企查查科技股份有限公司)",
      "公告类型": "监管问询",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2025-12-22"
    },
    {
      "公告标题": "北京德恒律师事务所关于企查查科技股份有限公司首次公开发行股票并在主板上市的法律意见书",
      "公告类型": "首发",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2025-10-10"
    },
    {
      "公告标题": "中信证券股份有限公司关于企查查科技股份有限公司首次公开发行股票并在主板上市的发行保荐书",
      "公告类型": "首发",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2025-10-10"
    },
    {
      "公告标题": "容诚会计师事务所(特殊普通合伙)关于企查查科技股份有限公司首次公开发行股票并在主板上市的财务报告及审计报告",
      "公告类型": "首发",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2025-10-10"
    },
    {
      "公告标题": "中信证券股份有限公司关于企查查科技股份有限公司首次公开发行股票并在主板上市的上市保荐书",
      "公告类型": "首发",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2025-10-10"
    },
    {
      "公告标题": "企查查科技股份有限公司主板首次公开发行股票招股说明书(申报稿)",
      "公告类型": "招股说明书、首发",
      "证券类型": "A股",
      "证券简称/代码": "",
      "日期": "2025-10-10"
    },
    {
      "公告标题": "关于企查查科技股份有限公司首次公开发行股票并上市辅导工作完成报告",
      "公告类型": "上市辅导",
      "证券类型": "上市辅导",
      "证券简称/代码": "",
      "日期": "2024-12-04"
    },
    {
      "公告标题": "关于企查查科技股份有限公司首次公开发行股票并上市辅导工作进展报告(第三期)",
      "公告类型": "上市辅导",
      "证券类型": "上市辅导",
      "证券简称/代码": "",
      "日期": "2024-10-12"
    },
    {
      "公告标题": "关于企查查科技股份有限公司首次公开发行股票并上市辅导工作进展报告(第二期)",
      "公告类型": "上市辅导",
      "证券类型": "上市辅导",
      "证券简称/代码": "",
      "日期": "2024-07-10"
    },
    {
      "公告标题": "关于企查查科技股份有限公司首次公开发行股票并上市辅导工作进展报告(第一期)",
      "公告类型": "上市辅导",
      "证券类型": "上市辅导",
      "证券简称/代码": "",
      "日期": "2024-04-11"
    },
    {
      "公告标题": "关于企查查科技股份有限公司首次公开发行股票并上市辅导备案报告",
      "公告类型": "上市辅导",
      "证券类型": "上市辅导",
      "证券简称/代码": "",
      "日期": "2023-12-19"
    }
  ]
}
"type": "text"
"resultType": "complete"

Response result

Response structure

Inferred from examples
  • _metaobject
    • io.modelcontextprotocol/serverInfoobject
      • iconsobject[]
        • mimeTypestring
        • sizesstring[]
        • srcstring
      • namestring
      • titlestring
      • versionstring
      • websiteUrlstring
  • contentobject[]
    • textstring
    • typestring
  • resultTypestring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use QCC — Company Announcements with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.