National Bidding and Tendering Project Query & Company Profile API

The Specific Problem Addressed

In scenarios involving supply chain analysis, market intelligence gathering, or commercial decision support, the systematic and rapid acquisition of public bidding, tendering, and contract information across a national scale is a fundamental yet cumbersome task. Data is typically scattered across various local public resource trading platforms, with non-uniform formats and field definitions. Engineers or analysts require a reliable structured data source to support competitor analysis, regional market insights, potential client discovery, or project lifecycle tracking. Manual collection is inefficient and hinders deep associative analysis.

Core Capabilities and Workflow

This skill encapsulates the ShiBo Technology bidding and tendering data API, providing a programmatic set of query and analysis interfaces. The workflow can be broken down into key steps:

1. Authentication and Configuration: The API key is read from the environment variable BBIAO_API_KEY. If not configured, guidance is provided for acquisition. The key is a prerequisite for all API calls.
2. Data Retrieval: Choose different search interfaces based on requirements.
   • Natural Language-Friendly Query: Use /bid/SearchProjectForAI, passing natural language parameters like areaName directly.
   • Structured Condition Query: Use /bid/searchProjectApi, supporting complex keyword combinations (e.g., keyword uses spaces for "must appear together" and | for "appear in either"), region codes (proviceCodeList), industry codes, enterprise roles (partAName, partBName, agentName), and time ranges. Search precision is controlled via searchType and searchMode.
   • AI-Assisted Query: First call /bid/aiSearchSubmitPolling to rewrite a vague requirement into structured conditions, then perform the search.
3. Deep Information Acquisition: Search results only return summaries. Based on the id and publishTime in the results, call detail interfaces as needed, for example:
   • /bid/getZTBStructreDetail to get structured fields like project budget, winning bid amount, party A & B, and agency information.
   • /bid/getZTBProjectDetail to get the full announcement text.
   • /bid/getZTBProjectFiles to get the list of attachments and download addresses.
   • /bid/getCollectUrl to get the original web page URL of the announcement.
4. Company Profile Construction: For a target enterprise, a profile can be built using a combination of interfaces:
   • /bid/companyProfileSummary for an overview including business basics and bidding statistics.
   • /bid/companyProfileContacts to obtain contact phone numbers.
   • /bid/companyProfileCustomers and /bid/companyProfileSuppliers to retrieve associated client and supplier enterprises and projects.
5. Assistance and Structurization: AI reasoning interfaces enhance query capabilities, such as mapping industry codes via /bid/industryReasoning or using /bid/ztbAiStructureInfo to extract structured fields from unstructured announcement text.

Applicable Boundaries and Considerations

• Nature of Data: The data is an aggregation of daily-updated public information. An "no match" return from an interface does not imply the real-world absence of relevant projects, only that the current query did not match any data. Analytical conclusions should explicitly state the data coverage scope and timeliness.
• Enterprise Relationships: The customer and supplier interfaces return business associations based on historical projects and do not signify equity control or current exclusive cooperative relationships. Confirming a specific project role (Party A/B) must be verified by calling the structured detail interface, and cannot be inferred solely from a companyName hit in the search.
• Usage Limits: All interfaces have pagination limits (e.g., list searches max 50 or 100 items per page). Full data retrieval requires iterative pagination. Before calculating statistics like market share, it is mandatory to confirm that all pages of data have been retrieved.
• Compliance: When using the enterprise contact interface, the user must ensure that subsequent communication complies with relevant privacy and marketing regulations.