Xunbiaobao: Precision Tender Sourcing and Customer Acquisition Engine

Problem

Bid notices, company entities, winning relationships, and price records are scattered across announcements and operational data. Sales, pre-sales, and marketing teams often need to answer who is buying, who is winning, which competitors are participating, and how brand and model prices are changing, but usually must search repeatedly and cross-check manually. This skill turns the 16 Zhiliaobiaoxun tender APIs into an executable workflow, combining keywords, entities, stages, and exclusions into precise queries.

How it works

It calls the base API with POST, preferring $ZLBX_API_KEY or local config; if missing, it asks before setting up a free trial. Core capabilities include:
- Bid search: search_bids, query_bids_advanced, and get_bid_detail retrieve notices by keyword, region, amount, time, and full text.
- Company analysis: search_company, get_company_profile, find_competitors, and find_potential_bidders map company profiles, competitors, and potential suppliers.
- Market analysis: get_top_purchasers, get_top_suppliers, get_top_brands, and get_price_trends reveal top buyers, winners, brands, and price history.
The key is match_modes: caller finds the procurer, while winner and tender find winning or bidding parties. keyword_groups and exclude_keywords support “must match all” and exclusion logic.

Caveats

It requires a valid API key; free quota can run out, and responses must handle INSUFFICIENT_BALANCE or RATE_LIMITED. It is best for objective bid data, entity relationships, and price statistics; company strategy and market forecasts should be cross-checked with public web sources.