QCC — Judgment Document Details

Retrieve the selected judgment document for the same company used in the document list query with the QCC API. Supports core judgment, claims and defenses, procedural history, or the complete document. Use it in a legal research or due diligence workflow. 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
The exact document ID returned by the judgment document list tool.
Company name or Unified Social Credit Code; must identify the same company as the judgment document list query.
Response section. Wire values: 核心裁判 (core judgment, default), 诉辩主张 (claims and defenses), 审理与执行经过 (trial and enforcement history), or 全部 (all).
Retrieve the selected judgment document for the same company used in the document list query. Supports core judgment, claims and defenses, procedural history, or the complete document.

Sample response

No response example is configured. A real response is available only after running the API, or when a published sample is added.

Response result

Response structure

No response structure is available yet. Run a request to inspect its response.

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 — Judgment Document Details with your agent

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