QCC — Company Entity Identification
Identify a company using its name, abbreviation, brand, stock abbreviation, or other keywords. Returns an exact match or up to five candidate entities.
- 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 — Company Entity Identification · 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/company/get_company_by_query' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"searchKey": "企查查"
}'- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/qcc/company/get_company_by_query- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/qcc/company/get_company_by_query' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"searchKey": "企查查"
}'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
searchKey | JSON request bodybody | string | Yes | Search keywords across company names, abbreviations, brands, stock abbreviations, and related identity fields. |
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": "{\"匹配结果\":\"多候选\",\"检索关键字\":\"企查查\",\"摘要\":\"命中多个相关主体,无法自动锁定。必须将候选列表完整展示给用户,等待用户明确指定后方可继续。自动选择任意候选项直接调用下游工具属于错误操作。\",\"企业信息\":[{\"企业名称\":\"企查查科技股份有限公司\",\"统一社会信用代码\":\"91320594088140947F\",\"成立日期\":\"2014-03-12\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"在业\"},{\"企业名称\":\"上海知彼网络科技有限公司\",\"统一社会信用代码\":\"91310105MA1FW0XD3D\",\"成立日期\":\"2015-12-10\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"存续\"},{\"企业名称\":\"苏州企查查数据科技有限公司\",\"统一社会信用代码\":\"91320594MA21M50H4M\",\"成立日期\":\"2020-06-02\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"在业\"},{\"企业名称\":\"北京知彼科技有限公司\",\"统一社会信用代码\":\"91110105696328177B\",\"成立日期\":\"2009-11-10\",\"法定代表人名称\":[\"杨京\"],\"状态\":\"存续\"},{\"企业名称\":\"企查查科技股份有限公司深圳分公司\",\"统一社会信用代码\":\"91440300MA5HA1R27N\",\"成立日期\":\"2022-04-19\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"存续\"}]}",
"type": "text"
}
],
"resultType": "complete"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# QCC — Company Entity Identification
Identify a company using its name, abbreviation, brand, stock abbreviation, or other keywords. Returns an exact match or up to five candidate entities.
## Available implementations
qcc · QCC — Company Entity Identification: https://openany.si/markets/apis/capabilities/qcc-company-entity-identification?offering=b007f4aa-9ba9-4890-b0c5-db60922603fe · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/qcc-company-entity-identification
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/qcc/company/get_company_by_query
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/company/get_company_by_query' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"searchKey": "企查查"
}'
```
## API contract
```json
{
"resource_type": "api",
"name": "QCC — Company Entity Identification",
"endpoint": "https://api.openany.si/v1/agent-apis/qcc/company/get_company_by_query",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Identify a company using its name, abbreviation, brand, stock abbreviation, or other keywords. Returns an exact match or up to five candidate entities.",
"json_schema": {
"properties": {
"searchKey": {
"description": "Search keywords across company names, abbreviations, brands, stock abbreviations, and related identity fields.",
"type": "string"
}
},
"required": [
"searchKey"
],
"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": {
"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": "{\"匹配结果\":\"多候选\",\"检索关键字\":\"企查查\",\"摘要\":\"命中多个相关主体,无法自动锁定。必须将候选列表完整展示给用户,等待用户明确指定后方可继续。自动选择任意候选项直接调用下游工具属于错误操作。\",\"企业信息\":[{\"企业名称\":\"企查查科技股份有限公司\",\"统一社会信用代码\":\"91320594088140947F\",\"成立日期\":\"2014-03-12\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"在业\"},{\"企业名称\":\"上海知彼网络科技有限公司\",\"统一社会信用代码\":\"91310105MA1FW0XD3D\",\"成立日期\":\"2015-12-10\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"存续\"},{\"企业名称\":\"苏州企查查数据科技有限公司\",\"统一社会信用代码\":\"91320594MA21M50H4M\",\"成立日期\":\"2020-06-02\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"在业\"},{\"企业名称\":\"北京知彼科技有限公司\",\"统一社会信用代码\":\"91110105696328177B\",\"成立日期\":\"2009-11-10\",\"法定代表人名称\":[\"杨京\"],\"状态\":\"存续\"},{\"企业名称\":\"企查查科技股份有限公司深圳分公司\",\"统一社会信用代码\":\"91440300MA5HA1R27N\",\"成立日期\":\"2022-04-19\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"存续\"}]}",
"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- Identify a company using its name, abbreviation, brand, stock abbreviation, or other keywords. Returns an exact match or up to five candidate entities.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/qcc/company/get_company_by_query' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ -H 'Accept: application/json' \ --data-raw '{ "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": "{\"匹配结果\":\"多候选\",\"检索关键字\":\"企查查\",\"摘要\":\"命中多个相关主体,无法自动锁定。必须将候选列表完整展示给用户,等待用户明确指定后方可继续。自动选择任意候选项直接调用下游工具属于错误操作。\",\"企业信息\":[{\"企业名称\":\"企查查科技股份有限公司\",\"统一社会信用代码\":\"91320594088140947F\",\"成立日期\":\"2014-03-12\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"在业\"},{\"企业名称\":\"上海知彼网络科技有限公司\",\"统一社会信用代码\":\"91310105MA1FW0XD3D\",\"成立日期\":\"2015-12-10\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"存续\"},{\"企业名称\":\"苏州企查查数据科技有限公司\",\"统一社会信用代码\":\"91320594MA21M50H4M\",\"成立日期\":\"2020-06-02\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"在业\"},{\"企业名称\":\"北京知彼科技有限公司\",\"统一社会信用代码\":\"91110105696328177B\",\"成立日期\":\"2009-11-10\",\"法定代表人名称\":[\"杨京\"],\"状态\":\"存续\"},{\"企业名称\":\"企查查科技股份有限公司深圳分公司\",\"统一社会信用代码\":\"91440300MA5HA1R27N\",\"成立日期\":\"2022-04-19\",\"法定代表人名称\":[\"陈德强\"],\"状态\":\"存续\"}]}", "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.