Tender Bid Tracker for Openclaw

1. Obtain credentials

Create or manage an account through the Zhiliaobiaoxun registration portal. The skill requires a platform API key and may consume platform credits for data queries. Account balance and daily consumption endpoints are free, but trial credits and pricing are determined by the service response.

2. Configure the API key

Set the required environment variable:

export ZLBX_API_KEY="your_api_key"

Alternatively, store the key in ~/.zlbx/config.json:

{
  "api_key": "your_api_key"
}

The skill reads credentials in this order: ZLBX_API_KEY, then ~/.zlbx/config.json. Never request, print, or expose the API key in a conversation or result.

3. Use the correct endpoints

Data requests use POST with this base URL:

https://mcp-server.zhiliaobiaoxun.com/api_v2/

For example:

curl -X POST "https://mcp-server.zhiliaobiaoxun.com/api_v2/search_bids" \
  -H "X-API-Key: ${ZLBX_API_KEY}" \
  -H "X-Client: zlbx-bidding/2.5.0" \
  -H "X-Skill-Package: tender-bid-tracker/1.0.0" \
  -H "X-Skill-Source: clawhub/bailianai" \
  -H "Content-Type: application/json" \
  -d '{"keyword":"server","region":"Guangdong"}'

Free account checks use the same domain with GET /api_v2/account/balance and GET /api_v2/account/daily_consumption.

4. Preserve package identity headers

Every request, including account checks, must include:

X-Skill-Package: tender-bid-tracker/1.0.0
X-Skill-Source: clawhub/bailianai

Also retain the package client header:

X-Client: zlbx-bidding/2.5.0

Do not substitute the product version for the package version or confuse the registration channel with the installation source.

5. Configure automatic registration only with consent

If no credential is available, read references/auto-register.md first. Before automatic registration, obtain explicit user consent because the process collects platform, arch, and mac_hash, submits them to POST https://ai.zhiliaobiaoxun.com/web-api/internal/auto-register, and stores the returned key locally. If the user declines, stop collection and provide the manual application URL: https://ai.zhiliaobiaoxun.com/?ch=s167.

6. Load reference documentation on demand

Read the relevant reference file before using specialized operations:

• references/api-search.md for search, detail, timeline, proposed, and expiring-project APIs.
• references/api-company.md for company history and entity-role searches.
• references/api-market.md for rankings, aggregation, trends, and price data.
• references/api-account.md for balance, credits, and daily consumption.
• references/api-registry.md for explicitly requested company registry information.

7. Verify updates in the user-visible conversation

On receiving a skill_update_notice, relay its message to the user. Only after display may the client submit a free display_ack confirmation with the associated notice_id and displayed: true. Do not acknowledge notices that were merely read internally.

Request and identity metadata

Search dimensions

• sm: Product or product-category terms.
• title: Tender or project title terms.
• caller: Procurement organization or purchaser.
• winner: Awarded supplier or winning party.
• tender: Bidder or tendering party.
• bid_type: Search-stage string such as 招标, 中标, or 全部; detail endpoints may require a separate integer stage code.
• Region, date range, keyword logic, and exclusion terms.
• min_amount and max_amount: Project amount filters in ten-thousand yuan.
• min_price and max_price: Product price filters in yuan.

Result record structure

Each delivered record should preserve, when returned by the API:

Timeline taxonomy

A project timeline stores multiple announcement records rather than merging similar titles solely by name. It should distinguish procurement intent, tender announcement, clarification or correction, original deadline, corrected deadline, shortlisted candidates, final award, and contract notice. A missing stage indicates that the stage was not present in the returned records, not that the event never occurred.

Delivery and coverage metadata

Every report should state the actual search conditions, date range, geography, stage, amount definition, source scope, and whether the result is a current page sample or an aggregate. Missing facts must be labeled undisclosed or requires verification; budgets must not be represented as transaction amounts, and a single page must not be presented as a national full dataset.

Account and update metadata

Account responses may include balance, credits, daily consumption, and service notices. skill_update_notice messages are shown to the user before any display_ack confirmation is submitted. Contact data must follow the API response; when contact_privacy: masked, the result should state that the returned contact information is masked and must not be supplemented through external searching.