QCC — Company Tender Search

Retrieve a previously identified company's tender notices using its returned company ID, with role, keyword, notice status, date, and region filters. The request takes a company ID. Use it for account research or company due diligence. 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
Company ID; must come from the company ID returned by search_companies, search_tenders, get_tender_detail, search_proposed_projects, or get_proposed_project_detail.
Optional parameters (7)
Publication date lower bound, YYYY-MM-DD. For the last year use the current date minus one year; for the last three months subtract three months; for since 2024 use 2024-01-01. Omit when no time restriction is specified.
bidStatuses array
Notice substatuses, more specific than infoTypes. The first four enum entries concern tender notices and the remaining six concern award notices. If both information types and substatuses are supplied, the more specific substatus takes priority.
Publication date upper bound, YYYY-MM-DD; must not precede beginDate. Supply only when an explicit cutoff date is requested; otherwise omit to include the latest records.
infoTypes array
Information types. May be omitted when bidStatuses is supplied; the server derives the types automatically.
keywords array
Product, service, or project keywords to search within this company's notices. Maximum 10 keywords, combined with OR.
regions array
Project location filter. Prefer complete Chinese administrative names starting at province level and including suffixes, e.g. 江苏省, 江苏省苏州市, 江苏省苏州市吴中区, or 上海市浦东新区. Complete an unambiguous Suzhou abbreviation to 江苏省苏州市; ask for clarification if ambiguous. Combine requested regions in one regions array using OR. Hong Kong, Macao, and Taiwan are unsupported.
Single company role code in tender notices: 1=procuring entity, 3=winning bidder, 4=agent, 8=bidder (including bidders, award candidates, and winners), 6=mentioned party. Omit for no restriction.
Retrieve a previously identified company's tender notices using its returned company ID, with role, keyword, notice status, date, and region filters.

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 — Company Tender Search with your agent

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