QCC — Submit Document Parsing

Submit a directly accessible document URL for parsing into Markdown with the QCC API. Supports asynchronous processing and optional waiting. local files require the separate local bridge. 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...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body* object
Required source for parse_document: one directly accessible HTTP(S) document URL. Supported types: pdf, png, jpg, jpeg, jfif, webp, doc, docx, xls, xlsx, wps, et. The URL must start with http:// or https:// and point to a readable, intact, unencrypted file without an opening password. Do not pass local paths, file:// URLs, localhost, loopback, link-local, LAN/private-network addresses, internal domains, or resources requiring local access, VPN, or internal DNS. Do not pass resources requiring login, cookies, custom headers, or interactive authorization, or webpages, directory/share pages, base64, streams, document contents, or multiple URLs. Temporary signed query parameters are allowed if the file is directly accessible; preserve the complete URL including its query parameters.
Whether to try waiting for parsing to complete in this call; defaults to false. false returns task_id after submission, with later retrieval through get_parse_result. true may be used when the user wants an immediate result or the document is small, but does not guarantee completion. If status=processing is returned, continue polling get_parse_result.
Submit a directly accessible document URL for parsing into Markdown. Supports asynchronous processing and optional waiting; local files require the separate local bridge.

Sample response

"# 第三节 经营情况讨论与分析\n报告期内,公司实现营业收入 12.5 亿元,同比增长 18.3%……\n\n## 主要财务指标\n| 指标 | 2024 年 | 2023 年 |\n| 营业收入 | 12.5 亿 | 10.2 亿 |\n| 净利润 | 1.8 亿 | 1.4 亿 |"

Response result

Response structure

Inferred from examples
responsestring

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 — Submit Document Parsing with your agent

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