Wenmai Alpha Xiaohongshu Pro Scraper

---
name: wenmai-alpha-xiaohongshu-pro-scraper
description: "小红书内容采集接口，用于查询笔记、关键词、账号及接口支持的互动和内容趋势数据。当用户提到小红书笔记、关键词热度、种草内容、达人研究、用户反馈、内容趋势或小红书数据采集时触发此技能。即使用户未明确提及接口，只要需要基于小红书公开内容开展消费者或趋势研究，也应触发此技能。"
metadata:
  author: wenmai-ai
  version: "1.0.0"
---

# Wenmai Alpha Xiaohongshu Pro Scraper

## Purpose
Use this Skill to fetch Xiaohongshu Pro Scraper data through Wenmai standard API. It is useful for 小红书笔记、关键词和内容趋势.

The Skill calls exactly one fixed standard API endpoint:

- Endpoint: `POST /wmapi/v1/alpha/xiaohongshu-pro-scraper`
- Auth: Header `secret-key: $WENMAI_API_KEY`
- Script: `scripts/alpha_xiaohongshu_pro_scraper.py`

## How To Run

请参考 https://skill.wenmai-ai.com/wenmaiskills/use_guide.html 获取 `secret-key`；额度或余额不足时，按该指南完成充值。运行脚本前，把复制的 key 导出为 `WENMAI_API_KEY`（或 `WENMAI_SECRET_KEY`）。

```bash
export WENMAI_API_KEY=sk-...
python3 scripts/alpha_xiaohongshu_pro_scraper.py '{"mode": "search", "keywords": ["AI"], "noteType": "不限", "sortType": "general", "timeFilter": "不限", "fetchComments": false, "maxItemsPerInput": 3}'
```

The script prints the raw Wenmai API response as formatted JSON. Read `references/api.md` when you need parameter details, field meanings, allowed values, defaults, request examples, or response fields.

## Parameter Rules

Required top-level fields: none documented by the API reference; pass at least one meaningful query, URL, ID, keyword, mode, or filter parameter from `references/api.md`.

Default assumptions: preserve the user's requested marketplace, country, language, URL list, keyword list, IDs, filters, pagination, and result limits. For scraper-style endpoints, avoid expanding result limits unless the user asks for a broader scrape.

## Extra-charge Parameter Rules

Treat `mode: "notes"` with `noteUrls` as an opt-in, separately billed full-note-detail capability. Treat `fetchComments: true` as additional paid detail processing. Do not infer or enable either capability automatically. Include it only when the user explicitly requests full note details or comments, and tell the user before the request that it is billed separately.

Do not quote or explain upstream prices, plans, tiers, or billing formulas.

## Response Rules

Present returned data in compact tables when the user asks for inspection or comparison. For long arrays, summarize the most decision-relevant rows first, then offer to continue with more rows. Keep raw numbers and source URLs traceable to response fields.

If the API response contains an `error` or a non-`OK` `code`, report the message and `requestId` if present, then suggest parameter corrections. Never invent missing data.