Local Tender Express Search

Problem

Local tender notices are scattered across regions and platforms. Sales and operations teams often spend time searching for projects, companies, brands, prices, and competitors. Manual workflows suffer from imprecise keyword matching, mixed announcement stages, and incomplete company coverage, which can hide renewal opportunities or distort market estimates.

How It Works

This skill wraps a set of POST tender APIs and turns structured queries into operational insights:

• Tender search: use search_bids and query_bids_advanced to filter by region, amount, time, and announcement stage.
• Company analysis: use search_company, find_competitors, and get_company_partners to cover headquarters and subsidiaries, then inspect bids, awards, suppliers, and contacts.
• Market and price analysis: use get_top_brands, get_price_trends, and aggregate_bids_advanced to compare brands, models, unit prices, and aggregated statistics.
• Key parameters: match_modes controls whether keywords hit caller, winner, tender, and related fields; keywords, keyword_groups, and exclude_keywords combine AND, OR, and exclusion logic.

After retrieving project lists or details, the workflow can drill down by company, brand, or stage.

Scope and Notes

The data is primarily public tender information and is best suited for project discovery, competitor monitoring, and market summaries. Strategic, policy, or financial analysis should still be supplemented with official websites, credible media, and industry sources. API access and quota behavior depend on the configured environment, so the source of the API Key and remaining quota should be checked before production use.