QCC — Randomized Inspections

Retrieve randomized inspections 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 randomized inspections 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
{
  "企业名称": "企查查科技股份有限公司",
  "摘要": "该查询实体共有6条双随机抽查记录。已为您完整呈现所有数据。",
  "双随机抽查信息": [
    {
      "计划编号": "32057120261011",
      "计划名称": "2026年大型企业年度报告公示信息检查",
      "任务编号": "320571202603241002",
      "任务名称": "2026年大型企业年度报告公示信息检查",
      "抽查类型": "定向",
      "抽查机关": "苏州工业园区市场监督管理局",
      "完成日期": "2026-08-14"
    },
    {
      "计划编号": "32000020251112",
      "计划名称": "大型企业公示信息联合检查",
      "任务编号": "320000202501211003",
      "任务名称": "大型企业公示信息联合检查",
      "抽查类型": "定向",
      "抽查机关": "苏州工业园区市场监督管理局",
      "完成日期": "2025-08-18"
    },
    {
      "计划编号": "32000020241246",
      "计划名称": "2024年电信业务经营许可检查",
      "任务编号": "320000202407301005",
      "任务名称": "2024年电信业务经营许可检查",
      "抽查类型": "定向",
      "抽查机关": "江苏省通信管理局",
      "完成日期": "2024-10-22"
    },
    {
      "计划编号": "32059420201002",
      "计划名称": "App违法违规收集使用个人信息专项治理“双随机、一公开”联合检查",
      "任务编号": "320594202005281006",
      "任务名称": "App专项治理双随机联合检查(企业监管辅助研判模型测评等级C)",
      "抽查类型": "定向",
      "抽查机关": "苏州工业园区文体旅游局",
      "完成日期": "2020-10-30"
    },
    {
      "计划编号": "32059420201002",
      "计划名称": "App违法违规收集使用个人信息专项治理“双随机、一公开”联合检查",
      "任务编号": "320594202005281006",
      "任务名称": "App专项治理双随机联合检查(企业监管辅助研判模型测评等级C)",
      "抽查类型": "定向",
      "抽查机关": "苏州工业园区公安局",
      "完成日期": "2020-10-29"
    },
    {
      "计划编号": "32059420201002",
      "计划名称": "App违法违规收集使用个人信息专项治理“双随机、一公开”联合检查",
      "任务编号": "320594202005281006",
      "任务名称": "App专项治理双随机联合检查(企业监管辅助研判模型测评等级C)",
      "抽查类型": "定向",
      "抽查机关": "苏州工业园区市场监督管理局",
      "完成日期": "2020-10-21"
    }
  ]
}
"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 — Randomized Inspections with your agent

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