BiaoBiaoDa Tender Opportunity Monitor

Problem

Tender and bid data are scattered across announcement stages and role fields. Searching keywords alone can mix purchasers, winners, and bidders, and it may miss subsidiaries, past suppliers, competitors, and brand price changes. When tracking customers, evaluating competition, or discovering opportunities, these missing relationships cause repeated gaps.

How it works

The skill calls authenticated ZLBX_API_KEY endpoints and organizes queries into three tasks:

• Bid search: use search_bids for basic retrieval and query_bids_advanced with keyword_groups and exclude_keywords for AND logic, exclusions, and filters; bid_process distinguishes stages such as intent, tender, award, and contract.
• Company analysis: search_company can cover headquarters and subsidiaries, then get_company_profile, get_company_partners, find_competitors, and find_potential_bidders reveal profiles, partners, competitors, and potential suppliers.
• Market and price: get_top_purchasers, get_top_suppliers, and get_top_brands show who buys, who wins, and which brands or models appear; get_price_trends returns historical award unit prices for brand and model combinations.

The key parameter is match_modes: caller finds projects issued by a company, winner finds awarded projects, tender finds bid projects, while brand, sm, and fulltext target brand, product name, and full-text scope. Choosing the right mode is more precise than adding more keywords.

Boundaries

Results depend on the platform's bid coverage, announcement delays, missing fields, quota, and rate limits. For trend, policy, or company-strategy analysis, use web search for context, but keep the interface's bid, award, and price data as the primary evidence.