National Bidding and Tender Information Search and Subscription Reminder

Specific Problem

Bidding and tender information updates over 300,000 records daily, making manual filtering and monitoring for specific industries or regions inefficient and prone to missing opportunities. Enterprise operations teams need automated tools to process vast data, quickly translate business needs into executable searches, and enable continuous tracking.

How This Skill Works

The skill integrates with the Shibo Technology bidding data API via BBIAO_API_KEY, offering a structured workflow:

• Input Parsing and Condition Generation: Extracts parameters like keyword, areaCode, and startDate from user natural language descriptions (e.g., "find construction tenders in Beijing for the last 7 days"), supporting exclusion and inclusion keywords for precise searches.
• API Calls and Data Retrieval: Executes POST /outer-gateway/bid/searchProjectApi for lists with pageNumber not exceeding 50; for high-relevance results, calls getZTBStructreDetail or getZTBProjectDetail for details, cleaning HTML tags before output.
• Result Processing and Subscription Generation: Deduplicates using id + publishTime, sorts by relevance, publication time, and amount matching, and generates reusable subscription rules (including query cycles and push frequencies). However, actual automatic pushing depends on the runtime platform's scheduled task capabilities.

Key steps include: reading the API key from environment variables, handling user timezone (default Asia/Shanghai), and returning results with project ID and original links for traceability.

Applicability and Limitations

• Data Dependency: Relies on Shibo Technology API with a valid key and quota; covers national bidding data, but field completeness is subject to API limits, e.g., contacts require additional calls.
• Subscriptions and Pushing: Generates subscription rules, but background scheduled tasks need user configuration; API failures output error messages without automatic retries.
• Usage Constraints: Search condition parsing may be ambiguous, requiring user confirmation; insufficient API balance prompts manual top-up without automatic payment handling.