mpstats
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseMPSTATS API
MPSTATS API
MPSTATS is a Russian marketplace analytics platform with data on Wildberries, Ozon, and Yandex Market: product research, category analysis, seller/brand monitoring, SKU-level sales, stock, and review data.
Work through the ready-made shell scripts in — call them via the Bash tool instead of writing HTTP code. Reference files in are API contracts only.
scripts/references/MPSTATS是一款俄罗斯电商平台分析工具,涵盖Wildberries、Ozon和Yandex Market的数据:包括产品调研、品类分析、卖家/品牌监控、SKU级别的销售、库存及评论数据。
请通过目录下的现成Shell脚本进行操作——使用Bash工具调用它们,无需编写HTTP代码。目录下的参考文件仅为API契约。
scripts/references/Token setup
Token配置
Scripts auto-load the token from via . A per-command env var overrides the file.
config/.envscripts/common.shMPSTATS_TOKENSetup and where to get the token: .
config/README.mdIf the token is missing, offer the user exactly 2 options before continuing:
- User sends the token in chat → agent creates itself.
config/.env - User runs locally: and pastes the token into
cp config/.env.example config/.env.config/.env
Token page: https://mpstats.io/userpanel (API token block). Requires an active MPSTATS subscription.
脚本会通过自动从加载Token。使用单个命令的环境变量可覆盖文件中的配置。
scripts/common.shconfig/.envMPSTATS_TOKEN配置方法及Token获取位置:。
config/README.md如果缺少Token,在继续操作前需向用户提供以下2个明确选项:
- 用户在聊天中发送Token → Agent自动创建文件。
config/.env - 用户本地运行:并将Token粘贴到
cp config/.env.example config/.env中。config/.env
Token页面:https://mpstats.io/userpanel (API token block)。需要有效MPSTATS订阅。
References
参考文档
API contracts (endpoints, params, response semantics) — read on demand:
- — base URL, auth headers, response codes, rate limits
references/auth.md - — common request/response model for all POST endpoints
references/pagination-filter-sort.md - ,
references/wb-categories.md,references/wb-brands-sellers.md— Wildberriesreferences/wb-similar-sku.md - ,
references/ozon-categories.md— Ozonreferences/ozon-brands-sellers-sku.md - — Yandex Market
references/ym-categories.md - — API limits
references/account.md - — what is wrapped by scripts vs. still uncovered
references/coverage.md - — how to format analytical answers and brand-styled HTML/PDF reports
references/presentation.md
API契约(端点、参数、响应语义)——按需查阅:
- —— 基础URL、认证头、响应码、请求频率限制
references/auth.md - —— 所有POST端点通用的请求/响应模型
references/pagination-filter-sort.md - ,
references/wb-categories.md,references/wb-brands-sellers.md—— Wildberries相关references/wb-similar-sku.md - ,
references/ozon-categories.md—— Ozon相关references/ozon-brands-sellers-sku.md - —— Yandex Market相关
references/ym-categories.md - —— API限制
references/account.md - —— 脚本已覆盖与未覆盖的功能
references/coverage.md - —— 分析结果及品牌风格HTML/PDF报告的格式规范
references/presentation.md
Result formatting
结果格式
Lead with a concise conclusion, then evidence. Use compact tables for multi-entity results, charts for trends/segmentation/comparisons. Don't dump raw JSON unless asked — interpret what the numbers mean for the decision. For HTML/PDF reports follow the MPSTATS brand style in .
references/presentation.md先给出简洁结论,再附上依据。多实体结果使用紧凑表格,趋势/细分/对比分析使用图表。除非用户要求,否则不要直接输出原始JSON——要解读数据对决策的意义。HTML/PDF报告需遵循中的MPSTATS品牌风格。
references/presentation.mdSanity check — flag anomalies, never report blindly
合理性校验——标记异常,绝不盲目报告
MPSTATS data can contain outliers, seller errors, unit mismatches, and stale rows. Reporting them as fact misleads the user. Before presenting any number, sanity-check its magnitude.
Flag explicitly when you see:
- Price far outside the category norm — e.g. napkins at 500 000 ₽ per item, a phone case at 50 ₽, a refrigerator at 200 ₽. Compare to the category median; if it's roughly >10× off, it is almost certainly a seller-side price error, a unit mismatch (pack vs piece), or a placeholder.
- Implausible volumes — a small seller suddenly at 1 000 000 units/month; revenue without sales; revenue ≠ approximately .
price × units - Zero / null / negative values where they shouldn't be — rating 0 on a SKU with reviews, stock = -5, "0 days since last sale" on an obviously inactive SKU.
- Date / period weirdness — requested period ≠ returned period, gaps in by-date series, future-dated rows.
- Unit mismatches — price per pack treated as price per piece; m² vs piece; liters vs ml.
How to flag, in this order:
- Show the anomalous row clearly, with the value called out (e.g. "500 000 ₽ за упаковку — похоже на ошибку ценника продавца").
- State your best guess at the cause (unit mismatch, seller error, stale data, placeholder).
- Either drop the row from aggregates (and say you did) or note that aggregates are skewed by it.
- Continue the analysis on cleaned data.
Do NOT silently drop or "round" anomalies. Do NOT report them as if they were real and let the user spot the absurdity. The conclusion must rely on cleaned data; the raw outlier is mentioned for transparency.
MPSTATS数据可能包含异常值、卖家错误、单位不匹配及过期数据。将此类数据如实报告会误导用户。在展示任何数据前,务必校验其合理性。
发现以下情况时需明确标记:
- 价格远超品类常规范围 —— 例如纸巾单价500000卢布,手机壳50卢布,冰箱200卢布。与品类中位数对比;若偏差超过约10倍,几乎可以确定是卖家定价错误、单位不匹配(包装 vs 单件)或占位符。
- 销量/收入不合理 —— 小卖家突然月销100万件;有收入无销量;收入与数值严重不符。
价格×销量 - 不应出现零/空/负值的字段 —— 有评论的SKU评分为0,库存=-5,明显 inactive 的SKU显示“距离上次销售0天”。
- 日期/周期异常 —— 请求周期与返回周期不符,按日期统计的数据存在缺口,出现未来日期的记录。
- 单位不匹配 —— 将包装单价当作单件单价;平方米 vs 件;升 vs 毫升。
标记步骤(按顺序):
- 清晰展示异常记录,并高亮异常值(例如:“500000卢布/包装——疑似卖家定价错误”)。
- 说明你对异常原因的最佳猜测(单位不匹配、卖家错误、过期数据、占位符)。
- 要么从汇总数据中移除该记录(并告知用户),要么注明汇总数据受其影响而失真。
- 使用清洗后的数据继续分析。
请勿默默删除或“修正”异常值。请勿将异常值当作真实数据报告,让用户自行发现问题。结论必须基于清洗后的数据;为保证透明度,需提及原始异常值。
Scripts
脚本
Ready-to-use shell scripts in . Call via the Bash tool, do not rewrite HTTP. Full catalog with per-script use-cases and routing guidance: . Run any script with for parameters.
scripts/scripts/README.md--help| Script | Purpose | Usage |
|---|---|---|
| Check API quota remaining | |
| Full WB category tree | |
| WB category products | |
| WB category breakdown (subcategories/brands/sellers/trends) | |
| WB SKU analytics (full/sales/balance/keywords/comments) | |
| WB card content (description, characteristics, dimensions) — uses WB CDN, not MPSTATS | |
| WB brand products or analytics | |
| WB seller products or analytics | |
| WB subjects/niches list for research | |
| WB subject endpoints ( | |
| WB similar families ( | |
| WB AI forecasts and season effects | |
| WB warehouse distribution for brand/seller | |
| WB period compare for category/brand/seller/subject | |
| Full Ozon category tree | |
| Ozon category products or stats | |
| Ozon SKU reports ( | |
| Ozon brand products or analytics | |
| Ozon seller products or analytics by seller id or name | |
| Ozon period compare for category/brand/seller | |
| Yandex Market category products or stats | |
| Yandex Market brand products or analytics | |
| Yandex Market seller products or analytics | |
| Yandex Market item sales history with optional dates | |
| Yandex Market period compare for category/brand/seller | |
| Universal raw API caller for any MPSTATS method/path | |
scripts/scripts/README.md--help| 脚本 | 用途 | 使用示例 |
|---|---|---|
| 查看剩余API配额 | |
| 获取完整WB品类树 | |
| 获取WB品类下的商品 | |
| WB品类细分分析(子品类/品牌/卖家/趋势) | |
| WB SKU分析(完整数据/销售/库存/关键词/评论) | |
| WB商品卡片内容(描述、参数、尺寸)——使用WB CDN,而非MPSTATS | |
| WB品牌商品或分析数据 | |
| WB卖家商品或分析数据 | |
| 获取WB可研究的主题/细分领域列表 | |
| WB主题端点( | |
| WB相似商品组( | |
| WB AI预测及季节影响分析 | |
| WB品牌/卖家的仓库分布 | |
| WB品类/品牌/卖家/主题的周期对比 | |
| 获取完整Ozon品类树 | |
| Ozon品类商品或统计数据 | |
| Ozon SKU报告( | |
| Ozon品牌商品或分析数据 | |
| 通过卖家ID或名称获取Ozon卖家商品或分析数据 | |
| Ozon品类/品牌/卖家的周期对比 | |
| Yandex Market品类商品或统计数据 | |
| Yandex Market品牌商品或分析数据 | |
| Yandex Market卖家商品或分析数据 | |
| Yandex Market商品销售历史(可指定日期) | |
| Yandex Market品类/品牌/卖家的周期对比 | |
| 通用原始API调用工具,支持任意MPSTATS方法/路径 | |