Jianyu Bidding Tender Data Query Radar

Problem

Tender and bid data is often split across announcement titles, company entities, procurement stages, and product fields. When an engineer needs to isolate a company’s published tenders, its winning or bidding records, expiring projects, and brand price trends, raw full-text search can pull in unrelated maintenance or consumable noise and make competitor or potential-supplier analysis unstable.

How It Works

The skill wraps 16 Jianyu Bidding API tools into three layers:
- Bid search: search_bids, query_bids_advanced, get_bid_detail, and search_expiring_projects cover keyword, region, amount, time, and announcement-stage filters.
- Company analysis: search_company, get_company_profile, find_competitors, and find_potential_bidders support entity matching, partners, competitors, and potential supplier recommendations.
- Market statistics: get_top_purchasers, get_top_suppliers, get_top_brands, aggregate_bids_advanced, and get_price_trends support top purchasers, suppliers, brands/models, and price trends.

The important control is match_modes, which constrains keywords to specific fields, such as caller for a purchaser’s tenders, winner or tender for a supplier’s wins or bids, and sm or brand for products and brands. Complex queries can combine keywords, keyword_groups, and exclude_keywords; AND-style grouping requires query_bids_advanced. Calls require an API key, quota errors are handled based on the key source, and common errors include RATE_LIMITED and INVALID_REQUEST; pagination uses page and page_size, with a maximum page_size of 50.

Limits

It is best suited for bid search, company relationship mapping, top purchaser/supplier/brand analysis, and price trends. For market forecasting, supply-chain analysis, or strategy assessment, treat tender data as primary evidence and supplement it with public web sources. It does not replace compliance review, contract verification, or commercial due diligence.