Biaozhaozhao Tender Quick Search Engine

Problem being solved

Bid information is fragmented across announcement titles, product names, brands, purchasers, winners, and bidders. A plain keyword search can mix in maintenance items, consumables, or unrelated same-name projects, and it does not easily reveal whether a company is buying, winning, competing, or what the market is paying. This skill turns those queries into a set of POST API tools that support field targeting, keyword logic, and stage filtering.

Core capabilities and key steps

• search_bids and query_bids_advanced support keywords, keyword_groups, and exclude_keywords: main keywords use OR logic, each group must match, and excluded terms filter out results.
• match_modes controls the searched field: sm for product, brand for brand, caller for purchaser, winner for awardee, tender for bidder, and fulltext for full-text search.
• Company tools such as search_company, get_company_profile, find_competitors, and find_potential_bidders support entity lookup, business keywords, partners, competitors, and potential suppliers.
• Market tools such as get_top_purchasers, get_top_suppliers, get_top_brands, and get_price_trends summarize top buyers, winning suppliers, brands and models, and historical unit prices.
• bid_process filters results by stages such as procurement intent, tender, award, and contract, reducing irrelevant announcements.

Boundaries and notes

• Use interface-returned bid, company, and market data as the primary evidence; use web search as a supplement for trends, strategy, or policy interpretation.
• Calls rely on an API key, preferring environment variables or local configuration; quota errors require checking the key source and the corresponding top-up or login path.
• keyword_groups requires the advanced search tool, and pagination should stay within the documented page_size limit to avoid rate limiting.