QCC — Company Registration Information

Retrieve core company registration details, including legal representative, registered capital, incorporation date, registration status, and registered address. Supply a search key. Sample fields include content and text. Use it in a legal research or due diligence workflow.

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 core company registration details, including legal representative, registered capital, incorporation date, registration status, and registered address.

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
{
  "企业名称": "企查查科技股份有限公司",
  "统一社会信用代码": "91320594088140947F",
  "法定代表人": "陈德强",
  "登记状态": "在业",
  "成立日期": "2014-03-12",
  "注册资本": "36225万元",
  "实缴资本": "36225万元",
  "组织机构代码": "08814094-7",
  "工商注册号": "320594000299470",
  "纳税人识别号": "91320594088140947F",
  "企业类型": "股份有限公司(非上市、自然人投资或控股)",
  "营业期限": "2014-03-12至无固定期限",
  "纳税人资质": "一般纳税人",
  "人员规模": "400-499人",
  "参保人数": "455",
  "分支机构参保人数": "12",
  "核准日期": "2026-08-07",
  "所属地区": "江苏省苏州市苏州工业园区",
  "地区信息": {
    "省份": "江苏省",
    "城市": "苏州市",
    "区域": "苏州工业园区",
    "地区代码": "320576"
  },
  "登记机关": "苏州市数据局",
  "支付系统行号": "",
  "进出口企业代码": "",
  "国标行业": {
    "门类": "信息传输、软件和信息技术服务业",
    "大类": "软件和信息技术服务业",
    "中类": "",
    "小类": ""
  },
  "企业简称": "企查查",
  "英文名": "Qichacha Tec Co., Ltd.",
  "注册地址": "中国(江苏)自由贸易试验区苏州片区苏州工业园区汇智街8号",
  "通信地址": "",
  "经营范围": "计算机软件开发、计算机信息技术服务;通信系统自动化软硬件的开发,并提供技术咨询、技术服务;计算机软硬件的销售及维护;软件设计及技术转让,并提供相关技术服务;企业管理咨询;市场调查;企业征信业务;企业信用评估;信用管理咨询。(依法须经批准的项目,经相关部门批准后方可开展经营活动)许可项目:互联网信息服务;第二类增值电信业务;广播电视节目制作经营(依法须经批准的项目,经相关部门批准后方可开展经营活动,具体经营项目以审批结果为准)一般项目:互联网数据服务;大数据服务;人工智能应用软件开发;人力资源服务(不含职业中介活动、劳务派遣服务);日用百货销售;玩具销售;互联网销售(除销售需要许可的商品)(除依法须经批准的项目外,凭营业执照依法自主开展经营活动)"
}
"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 Registration Information with your agent

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