QCC — Standards

Retrieve standards 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 standards 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
{
  "企业名称": "企查查科技股份有限公司",
  "摘要": "该查询实体共有9条标准信息记录。",
  "标准信息": [
    {
      "标准号": "T/ZGCMCA 011—2025",
      "级别": "团体标准",
      "属性": "",
      "名称": "人工智能 智能体能力要求",
      "发布日期": "2026-04-16",
      "标准状态": "现行"
    },
    {
      "标准号": "T/ZGCMCA 006—2025",
      "级别": "团体标准",
      "属性": "",
      "名称": "人工智能大模型 数据标注技术要求",
      "发布日期": "2026-02-07",
      "标准状态": "现行"
    },
    {
      "标准号": "T/ZGCMCA 011—2024",
      "级别": "团体标准",
      "属性": "",
      "名称": "数据要素 湖仓一体技术要求",
      "发布日期": "2025-09-25",
      "标准状态": "现行"
    },
    {
      "标准号": "T/ZGCMCA 010—2024",
      "级别": "团体标准",
      "属性": "",
      "名称": "数据要素 数据安全治理架构应用导则",
      "发布日期": "2025-09-25",
      "标准状态": "现行"
    },
    {
      "标准号": "T/ZGCMCA 005—2024",
      "级别": "团体标准",
      "属性": "",
      "名称": "数据要素 数据治理体系建设规范",
      "发布日期": "2025-09-25",
      "标准状态": "现行"
    },
    {
      "标准号": "T/ZGCMCA 002—2024",
      "级别": "团体标准",
      "属性": "",
      "名称": "数据要素 数据登记确权管理要求",
      "发布日期": "2025-04-11",
      "标准状态": "现行"
    },
    {
      "标准号": "T/ZGCMCA 003—2024",
      "级别": "团体标准",
      "属性": "",
      "名称": "数据要素 数据系统平台建设开发指南",
      "发布日期": "2025-04-11",
      "标准状态": "现行"
    },
    {
      "标准号": "T/ZGCMCA 0014—2024",
      "级别": "团体标准",
      "属性": "",
      "名称": "移动互联网应用程序(App)生命周期技术要求",
      "发布日期": "2024-12-01",
      "标准状态": "现行"
    },
    {
      "标准号": "Q/QCC0001S-2022",
      "级别": "企业标准",
      "属性": "",
      "名称": "信息技术 智能移动终端应用软件(APP)技术要求",
      "发布日期": "2022-07-27",
      "标准状态": "现行有效"
    }
  ]
}
"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 — Standards with your agent

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