QCC — Contact Information

Retrieve company phone numbers, usage labels, email addresses, websites, official-site indicators, and filing information 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.
Whether to exclude phone numbers known to be invalid. Set true when the user asks to remove invalid or incorrect numbers or dirty data. Omit or set false when all numbers are requested or no preference is stated. true removes only numbers confirmed invalid; numbers without a confirmed problem, including inconclusive cases, remain.
Retrieve company phone numbers, usage labels, email addresses, websites, official-site indicators, and filing information. Confirmed invalid phone numbers may be excluded.

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
{
  "企业名称": "企查查科技股份有限公司",
  "摘要": "该查询实体共有3类联系方式,共计12条记录,其中电话共计1条记录,邮箱共计3条记录,网址共计8条记录。",
  "联系方式信息": {
    "电话": [
      {
        "电话号码": "4009282212",
        "标签": [
          "客服"
        ]
      }
    ],
    "邮箱": [
      {
        "邮箱": "[email protected]"
      },
      {
        "邮箱": "[email protected]"
      },
      {
        "邮箱": "[email protected]"
      }
    ],
    "网址": [
      {
        "网址": "https://www.qcc.com",
        "网站描述": "企业网址",
        "是否是官网": "是",
        "ICP备案": "是"
      },
      {
        "网址": "www.greatld.com",
        "网站描述": "企查查科技有限公司",
        "是否是官网": "否",
        "ICP备案": "是"
      },
      {
        "网址": "www.biaozhaozhao.com",
        "网站描述": "标找找",
        "是否是官网": "否",
        "ICP备案": "是"
      },
      {
        "网址": "www.qcckyc.com",
        "网站描述": "知彼尽职调查",
        "是否是官网": "否",
        "ICP备案": "是"
      },
      {
        "网址": "www.qcc.cn",
        "网站描述": "企查查网",
        "是否是官网": "否",
        "ICP备案": "是"
      },
      {
        "网址": "www.qichacha.com",
        "网站描述": "企查查网",
        "是否是官网": "否",
        "ICP备案": "是"
      },
      {
        "网址": "www.qcc.com",
        "网站描述": "企查查网",
        "是否是官网": "否",
        "ICP备案": "是"
      },
      {
        "网址": "www.qichacha.net",
        "网站描述": "企查查网",
        "是否是官网": "否",
        "ICP备案": "是"
      }
    ]
  }
}
"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 — Contact Information with your agent

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