QCC — Executive — Related-Company Risk Scan
Retrieve related-company risk scan for a named director, supervisor, or senior executive. Both the company identity and person name anchor the query.
- Selected price
- $0 / callPublished pricing
- Providers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Provider | Price / call | Requests · 30d | Performance | Access |
|---|---|---|---|---|
qccCurrent QCC — Executive — Related-Company Risk Scan · POST | $0 / call | — | —successP50— |
Statistics use persisted gateway logs from the last 30 days up to now, including today.
Success rate = successful requests / all requests;
P50 = median latency of successful requests.
Prices reflect the published API contract. Contract revision: 3. Price update time: not supplied.
Playground
Run sends a real API request. Charges follow the published API contract.
curl \
'https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_related_risk_scan' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"personName": "陈德强",
"searchKey": "企查查科技股份有限公司"
}'- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_related_risk_scan- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_related_risk_scan' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"personName": "陈德强",
"searchKey": "企查查科技股份有限公司"
}'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
personName | JSON request bodybody | string | Yes | Director, supervisor, or senior executive name. Use together with searchKey to identify the correct person and avoid namesake matches. |
searchKey | JSON request bodybody | string | Yes | Company full registered name or Unified Social Credit Code. |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Published response example · Documented HTTP 200; not a live result. Published documentation example. Verify the actual response after an approved call.
{
"_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": [
{
"text": "{\"企业名称\":\"企查查科技股份有限公司\",\"人员名称\":\"陈德强\",\"能力声明\":\"关联方定位仅覆盖 失信被执行人/严重违法/破产重整/税收违法/被执行人/终本案件/股权冻结 7 维（每维最多前 10 · 按本维度条目数降序）；其余维度仅提供计数。定位清单外的关联方可由用户显式指定名称后单点查询，或经企查查页面查看。\",\"摘要\":\"陈德强名下有风险的关联方共 2 个。涉及重点关联风险维度 0 条记录，其中失信被执行人 0 条（涉 0 个关联方），严重违法 0 条（涉 0 个关联方），破产重整 0 条（涉 0 个关联方），税收违法 0 条（涉 0 个关联方），被执行人 0 条（涉 0 个关联方），终本案件 0 条（涉 0 个关联方），股权冻结 0 条（涉 0 个关联方）。\",\"有风险关联方数\":\"2\",\"维度计数汇总\":{\"关键风险\":{\"失信被执行人\":\"0\",\"被执行人\":\"0\",\"限制高消费\":\"0\",\"严重违法\":\"0\",\"税收违法\":\"0\",\"行政处罚\":\"0\",\"破产重整\":\"0\",\"终本案件\":\"0\",\"股权冻结\":\"0\",\"欠税公告\":\"0\",\"经营异常\":\"0\",\"惩戒名单\":\"0\"},\"司法案件\":[{\"类型\":\"知识产权纠纷（被告）\",\"条目数\":\"4\"},{\"类型\":\"侵权责任纠纷（被告）\",\"条目数\":\"7\"},{\"类型\":\"其他纠纷（被告）\",\"条目数\":\"11\"},{\"类型\":\"劳动纠纷（被告）\",\"条目数\":\"1\"}],\"其他关联风险\":[]},\"重点维度关联方定位\":[{\"维度\":\"失信被执行人\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"严重违法\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"破产重整\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"税收违法\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"被执行人\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"终本案件\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"股权冻结\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]}]}",
"type": "text"
}
],
"resultType": "complete"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# QCC — Executive — Related-Company Risk Scan
Retrieve related-company risk scan for a named director, supervisor, or senior executive. Both the company identity and person name anchor the query.
## Available implementations
qcc · QCC — Executive — Related-Company Risk Scan: https://openany.si/markets/apis/capabilities/qcc-executive-related-company-risk-scan?offering=1269561b-3c51-4c1a-9c9c-bdd39bcb1056 · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/qcc-executive-related-company-risk-scan
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_related_risk_scan
Price: $0 / call
Provider: qcc
Contract revision: 3
Price source: selected implementation in the OpenAny public API catalog. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_related_risk_scan' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"personName": "陈德强",
"searchKey": "企查查科技股份有限公司"
}'
```
## API contract
```json
{
"resource_type": "api",
"name": "QCC — Executive — Related-Company Risk Scan",
"endpoint": "https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_related_risk_scan",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Retrieve related-company risk scan for a named director, supervisor, or senior executive. Both the company identity and person name anchor the query.",
"json_schema": {
"properties": {
"personName": {
"description": "Director, supervisor, or senior executive name. Use together with searchKey to identify the correct person and avoid namesake matches.",
"type": "string"
},
"searchKey": {
"description": "Company full registered name or Unified Social Credit Code.",
"type": "string"
}
},
"required": [
"searchKey",
"personName"
],
"type": "object"
},
"location": "body",
"name": "body",
"nullable": false,
"pointer": "",
"required": true,
"type": "object"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "0",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Documentation example",
"request": {
"body": {
"personName": "陈德强",
"searchKey": "企查查科技股份有限公司"
},
"headers": {
"Accept": "application/json"
},
"path": {},
"query": {}
},
"response_body": {
"_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": [
{
"text": "{\"企业名称\":\"企查查科技股份有限公司\",\"人员名称\":\"陈德强\",\"能力声明\":\"关联方定位仅覆盖 失信被执行人/严重违法/破产重整/税收违法/被执行人/终本案件/股权冻结 7 维（每维最多前 10 · 按本维度条目数降序）；其余维度仅提供计数。定位清单外的关联方可由用户显式指定名称后单点查询，或经企查查页面查看。\",\"摘要\":\"陈德强名下有风险的关联方共 2 个。涉及重点关联风险维度 0 条记录，其中失信被执行人 0 条（涉 0 个关联方），严重违法 0 条（涉 0 个关联方），破产重整 0 条（涉 0 个关联方），税收违法 0 条（涉 0 个关联方），被执行人 0 条（涉 0 个关联方），终本案件 0 条（涉 0 个关联方），股权冻结 0 条（涉 0 个关联方）。\",\"有风险关联方数\":\"2\",\"维度计数汇总\":{\"关键风险\":{\"失信被执行人\":\"0\",\"被执行人\":\"0\",\"限制高消费\":\"0\",\"严重违法\":\"0\",\"税收违法\":\"0\",\"行政处罚\":\"0\",\"破产重整\":\"0\",\"终本案件\":\"0\",\"股权冻结\":\"0\",\"欠税公告\":\"0\",\"经营异常\":\"0\",\"惩戒名单\":\"0\"},\"司法案件\":[{\"类型\":\"知识产权纠纷（被告）\",\"条目数\":\"4\"},{\"类型\":\"侵权责任纠纷（被告）\",\"条目数\":\"7\"},{\"类型\":\"其他纠纷（被告）\",\"条目数\":\"11\"},{\"类型\":\"劳动纠纷（被告）\",\"条目数\":\"1\"}],\"其他关联风险\":[]},\"重点维度关联方定位\":[{\"维度\":\"失信被执行人\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"严重违法\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"破产重整\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"税收违法\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"被执行人\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"终本案件\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"股权冻结\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]}]}",
"type": "text"
}
],
"resultType": "complete"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Documentation example
Published documentation example. Verify the actual response after an approved call.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 1
Review these request fields before running. Keep the published provider and request method unchanged.
body- Retrieve related-company risk scan for a named director, supervisor, or senior executive. Both the company identity and person name anchor the query.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_related_risk_scan' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ -H 'Accept: application/json' \ --data-raw '{ "personName": "陈德强", "searchKey": "企查查科技股份有限公司" }'Check the response
Published response example · Documented HTTP 200; not a live result.
Sample response · not a live result{ "_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": [ { "text": "{\"企业名称\":\"企查查科技股份有限公司\",\"人员名称\":\"陈德强\",\"能力声明\":\"关联方定位仅覆盖 失信被执行人/严重违法/破产重整/税收违法/被执行人/终本案件/股权冻结 7 维（每维最多前 10 · 按本维度条目数降序）；其余维度仅提供计数。定位清单外的关联方可由用户显式指定名称后单点查询，或经企查查页面查看。\",\"摘要\":\"陈德强名下有风险的关联方共 2 个。涉及重点关联风险维度 0 条记录，其中失信被执行人 0 条（涉 0 个关联方），严重违法 0 条（涉 0 个关联方），破产重整 0 条（涉 0 个关联方），税收违法 0 条（涉 0 个关联方），被执行人 0 条（涉 0 个关联方），终本案件 0 条（涉 0 个关联方），股权冻结 0 条（涉 0 个关联方）。\",\"有风险关联方数\":\"2\",\"维度计数汇总\":{\"关键风险\":{\"失信被执行人\":\"0\",\"被执行人\":\"0\",\"限制高消费\":\"0\",\"严重违法\":\"0\",\"税收违法\":\"0\",\"行政处罚\":\"0\",\"破产重整\":\"0\",\"终本案件\":\"0\",\"股权冻结\":\"0\",\"欠税公告\":\"0\",\"经营异常\":\"0\",\"惩戒名单\":\"0\"},\"司法案件\":[{\"类型\":\"知识产权纠纷（被告）\",\"条目数\":\"4\"},{\"类型\":\"侵权责任纠纷（被告）\",\"条目数\":\"7\"},{\"类型\":\"其他纠纷（被告）\",\"条目数\":\"11\"},{\"类型\":\"劳动纠纷（被告）\",\"条目数\":\"1\"}],\"其他关联风险\":[]},\"重点维度关联方定位\":[{\"维度\":\"失信被执行人\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"严重违法\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"破产重整\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"税收违法\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"被执行人\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"终本案件\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]},{\"维度\":\"股权冻结\",\"本维度条目数\":\"0\",\"命中关联方数\":\"0\",\"展示声明\":\"已全量列出本维度命中的 0 个关联方\",\"关联方\":[]}]}", "type": "text" } ], "resultType": "complete" }
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.