QCC — Executive — High Consumption Restrictions
Retrieve high consumption restrictions for a named director, supervisor, or senior executive with the QCC API. Supply a person name and 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...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
qccCurrent QCC — Executive — High Consumption Restrictions · POST | $0 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
_metaobjectio.modelcontextprotocol/serverInfoobjecticonsobject[]mimeTypestringsizesstring[]srcstring
namestringtitlestringversionstringwebsiteUrlstring
contentobject[]textstringtypestring
resultTypestring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
_meta?: {
"io.modelcontextprotocol/serverInfo"?: {
icons?: Array<{
mimeType?: string;
sizes?: Array<string>;
src?: string;
}>;
name?: string;
title?: string;
version?: string;
websiteUrl?: string;
};
};
content?: Array<{
text?: string;
type?: string;
}>;
resultType?: string;
};- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_high_consumption_ban- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_high_consumption_ban' \
-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
Sample response · Documented HTTP 200 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": "{\"企业名称\":\"企查查科技股份有限公司\",\"人员名称\":\"陈德强\",\"搜索结果\":\"已全量扫描该主体董监高-限制高消费数据库,未发现任何记录。\"}",
"type": "text"
}
],
"resultType": "complete"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# QCC — Executive — High Consumption Restrictions
Retrieve high consumption restrictions for a named director, supervisor, or senior executive with the QCC API. Supply a person name and a search key. Sample fields include content and text. Use it for account research or company due diligence.
## Available implementations
qcc · QCC — Executive — High Consumption Restrictions: https://openany.si/markets/apis/capabilities/qcc-executive-high-consumption-restrictions?offering=2a6c739d-97bf-4439-9e22-e7048764e43b · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/qcc-executive-high-consumption-restrictions
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_high_consumption_ban
Price: $0 / call
Provider: qcc
Contract revision: 4
Price source: OpenAny public API contract and documented provider unit rates. 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_high_consumption_ban' \
-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 — High Consumption Restrictions",
"endpoint": "https://api.openany.si/v1/agent-apis/qcc/executive/get_executive_high_consumption_ban",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Retrieve high consumption restrictions 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": "{\"企业名称\":\"企查查科技股份有限公司\",\"人员名称\":\"陈德强\",\"搜索结果\":\"已全量扫描该主体董监高-限制高消费数据库,未发现任何记录。\"}",
"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 high consumption restrictions 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_high_consumption_ban' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ -H 'Accept: application/json' \ --data-raw '{ "personName": "陈德强", "searchKey": "企查查科技股份有限公司" }'Check the response
Sample response · Documented HTTP 200
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": [ { "text": "{\"企业名称\":\"企查查科技股份有限公司\",\"人员名称\":\"陈德强\",\"搜索结果\":\"已全量扫描该主体董监高-限制高消费数据库,未发现任何记录。\"}", "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.
Use QCC — Executive — High Consumption Restrictions with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.