Authoritative Procurement Policy and Bid Data Guide

Problem

Procurement data is scattered across announcements, with ambiguous roles such as buyer, supplier, and tenderer. Engineers often stitch together keywords, distinguish caller from winner, and derive company, brand, and price signals from bid records. This skill wraps Yuanbowang bid-data APIs into focused tools for bid search, company analysis, and market aggregation.

How It Works

• Bid search: use search_bids, query_bids_advanced, and get_bid_detail to filter by keyword, region, amount, and time, with match_modes controlling field targets such as caller, winner, and tender.
• Company analysis: use search_company, find_competitors, and get_company_contacts to profile entities, competitors, partners, and contacts.
• Market analysis: use get_top_suppliers, get_top_brands, get_price_trends, and aggregate_bids_advanced for top units, brands, models, and price history.
  Key steps are selecting the right tool, then combining keywords, keyword_groups, and exclude_keywords for OR, AND, and exclusion logic. An API key may come from an environment variable or local config; if absent, the skill asks before setting up a trial account.

Boundaries

The skill is strongest for objective bid records, company participation, brand rankings, pricing, and expiring projects. For strategy, policy impact, or industry rankings, supplement with reputable web sources. Responses respect page_size and error codes; quota or rate-limit errors should be handled according to key source, and auto-setup should not be applied when a manual key already exists.