QCC — Beneficial Owners

Retrieve natural-person beneficial owners and ultimate beneficial ownership percentages for the company 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 natural-person beneficial owners and ultimate beneficial ownership percentages for the company.

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
{
  "企业名称": "企查查科技股份有限公司",
  "摘要": "已识别出1名受益所有人。受益所有人名称陈德强,最终受益股份47.6955%。",
  "受益所有人信息": {
    "受益所有人": [
      {
        "受益所有人名称": "陈德强",
        "受益类型": [
          "25%以上股权、股份或合伙权益",
          "25%以上表决权、收益权",
          "单独或联合进行实际控制"
        ],
        "最终受益股份": "47.6955%",
        "表决权比例": "53.0011%",
        "任职类型": "法定代表人、董事长",
        "受益所有权形成日期": "2015-05-05"
      }
    ],
    "日常经营管理人员": [
      {
        "名称": "陈德强",
        "任职类型": "法定代表人、董事长"
      },
      {
        "名称": "杨京",
        "任职类型": "经理、董事"
      },
      {
        "名称": "施阳",
        "任职类型": "董事、副经理"
      },
      {
        "名称": "杨思超",
        "任职类型": "董事"
      },
      {
        "名称": "张浩",
        "任职类型": "董事"
      },
      {
        "名称": "马群",
        "任职类型": "董事"
      },
      {
        "名称": "宋瑜",
        "任职类型": "董事"
      },
      {
        "名称": "王洪成",
        "任职类型": "董事"
      },
      {
        "名称": "邱晶晶",
        "任职类型": "职工董事"
      }
    ]
  }
}
"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 — Beneficial Owners with your agent

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