QCC — Get Document Parsing Result
Retrieve the state and Markdown output of a task created by parse_document using its exact task_id with the QCC API. Result polling does not consume points. Use the result as input for a related analysis or application. Use the results to organize a research workflow and cross-check the relevant source records.
- Selected price
- $0 / callPublished pricing
- Sellers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
qccCurrent QCC — Get Document Parsing Result · POST | $0 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
responsestring// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = string;- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/qcc/document/get_parse_result- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/qcc/document/get_parse_result' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"task_id": "TASK_ID"
}'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
task_id | JSON request bodybody | string | Yes | The exact task ID returned by parse_document. Preserve it unchanged when querying task status or results. Do not fabricate, truncate, translate, or replace it with a filename, URL, document ID, or internal upstream task ID. |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Configured HTTP 200; actual status is unverified. Published documentation example. Verify the actual response after an approved call.
"# 第三节 经营情况讨论与分析\n报告期内,公司实现营业收入 12.5 亿元,同比增长 18.3%……\n\n## 主 要财务指标\n| 指标 | 2024 年 | 2023 年 |\n| 营业收入 | 12.5 亿 | 10.2 亿 |\n| 净利润 | 1.8 亿 | 1.4 亿 |"Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# QCC — Get Document Parsing Result
Retrieve the state and Markdown output of a task created by parse_document using its exact task_id with the QCC API. Result polling does not consume points. Use the result as input for a related analysis or application. Use the results to organize a research workflow and cross-check the relevant source records.
## Available implementations
qcc · QCC — Get Document Parsing Result: https://openany.si/markets/apis/capabilities/qcc-get-document-parsing-result?offering=ae1c1991-8906-4c8e-bd59-7df6407e3d8d · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/qcc-get-document-parsing-result
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/qcc/document/get_parse_result
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/document/get_parse_result' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"task_id": "TASK_ID"
}'
```
## API contract
```json
{
"resource_type": "api",
"name": "QCC — Get Document Parsing Result",
"endpoint": "https://api.openany.si/v1/agent-apis/qcc/document/get_parse_result",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Retrieve the state and Markdown output of a task created by parse_document using its exact task_id. Result polling does not consume points.",
"json_schema": {
"additionalProperties": false,
"properties": {
"task_id": {
"description": "The exact task ID returned by parse_document. Preserve it unchanged when querying task status or results. Do not fabricate, truncate, translate, or replace it with a filename, URL, document ID, or internal upstream task ID.",
"type": "string"
}
},
"required": [
"task_id"
],
"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": "Doc example (source abbreviated; HTTP status set during import)",
"request": {
"body": {
"task_id": "TASK_ID"
},
"headers": {
"Accept": "application/json"
},
"path": {},
"query": {}
},
"response_body": "# 第三节 经营情况讨论与分析\n报告期内,公司实现营业收入 12.5 亿元,同比增长 18.3%……\n\n## 主要财务指标\n| 指标 | 2024 年 | 2023 年 |\n| 营业收入 | 12.5 亿 | 10.2 亿 |\n| 净利润 | 1.8 亿 | 1.4 亿 |"
}
]
}
```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. |
Doc example (source abbreviated; HTTP status set during import)
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 the state and Markdown output of a task created by parse_document using its exact task_id. Result polling does not consume points.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/qcc/document/get_parse_result' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ -H 'Accept: application/json' \ --data-raw '{ "task_id": "TASK_ID" }'Check the response
Sample response · Configured HTTP 200; actual status is unverified.
Sample response"# 第三节 经营情况讨论与分析\n报告期内,公司实现营业收入 12.5 亿元,同比增长 18.3%……\n\n## 主要财务指标\n| 指标 | 2024 年 | 2023 年 |\n| 营业收入 | 12.5 亿 | 10.2 亿 |\n| 净利润 | 1.8 亿 | 1.4 亿 |"
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 — Get Document Parsing Result with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.