Marketplaces RU (WB, Ozon, Avito)
@marketplace-ru
Work with the big Russian marketplaces via their APIs — Wildberries, Ozon, Avito. Scans WB niches via the public catalog (no auth) and calls seller/analytics APIs (WB statistics/analytics, Ozon seller, Avito) with the user's tokens. Use when the user is a seller or researcher asking about competitor pricing, niche demand, product search at scale, «аналитика маркетплейсов», «посмотри нишу на WB», «конкуренты по товару», «мои продажи на Ozon», or pastes a seller API token. Do NOT use for personal shopping or price comparison of one item (smart-shopper), gift ideas (gift-finder), or general web search.
Who the Marketplaces RU skill is for
- Wildberries and Ozon sellers — assess a niche and competitors before launching a product, and make sense of their own sales analytics.
- Marketplace startups — understand demand, prices and how crowded a category is at the start.
- Analysts and brand managers — pull the top products and brands for a query into one comparison table.
What goes into the research
- Public WB scan — the Wildberries catalog with no authorization: up to 100 products per query with name, brand, rating and review count.
- Top brands and products — a summary table to gauge how crowded and competitive a niche is.
- Seller analytics — WB statistics and analytics API calls, Ozon seller APIs and Avito, all with your tokens.
- Prices and demand — compare competitor positions by price, rating and reviews.
How it works
The skill helps you plan and run the research, structure the data and explain the steps of working with marketplaces. The public Wildberries niche scan needs no authorization and fits a quick demand check. Deep seller analytics needs your own API token — the skill points you to where to get one and which calls to use, but it never stores or logs tokens. The skill does not connect to your account automatically, does not publish cards, and does not fake ratings or reviews — it's an assistant for honest research, not a manipulation tool.
Useful landmarks
- Verify API method versions against the platform's docs before relying on them — they change.
- Cache instead of polling — marketplace analytics endpoints are rate-limited.
- Data is for research — respect each platform's terms and don't republish raw dumps.
- Region and warehouse shift the WB results — account for the region parameter when comparing prices.
Related skills: ads strategy, ads analytics. For marketplace promotion — ad creatives and Avito listings.
Ready to research a niche? Launch the Marketplaces RU skill and describe the category.
Does the skill manage marketplace cards and cabinets?
No. The skill helps research niches, structure the data and explain the steps of working with marketplace analytics. It does not connect to your account automatically, does not publish or edit product cards, and does not fake ratings or reviews. Seller data is requested with your own API tokens.
Can I research a Wildberries niche without authorization?
Yes. Through the public WB catalog you can pull up to 100 products and the top brands for a query — no token needed. The response includes the name, brand, rating and review count. That's enough to estimate demand and competition at the start.
Do I need tokens for sales analytics?
Yes — seller analytics needs your own token for the relevant platform (WB, Ozon or Avito). The skill explains where and how to get each token, which calls are available and how to reconcile the data with your cabinet. Tokens are never logged or stored.
Which platforms are supported?
Wildberries (public catalog plus seller statistics and analytics APIs), Ozon (product and analytics seller APIs) and Avito (API with client_credentials auth). It's worth checking the exact method versions against each platform's docs — they change.
What else is the skill useful for?
Finding a niche before launching a product, assessing competitors and their prices, analyzing demand by region and warehouse, and explaining how to work with seller reports. Data is used for research within each platform's rules — no republishing raw dumps.
Is it paid?
You use the skill within your AgentHere plan — you pay tokens as the agent works. See the pricing page for limits.
Russian marketplaces — WB · Ozon · Avito
You help the user research and operate on the big Russian marketplaces.
Wildberries — public niche scan (NO auth)
Reliable public endpoint — use it for product/niche research without any token:
GET https://search.wb.ru/exactmatch/ru/common/v4/search
?ab_testing=false&appType=1&curr=rub&dest=-1257786
&query=<urlencoded>&resultset=catalog&sort=popular&spp=30&suppressSpellcheck=false
Returns up to 100 products with id, brand, name, rating, feedbacks. (dest = region/warehouse cluster; -1257786 is a safe default.) Prices are not in the search response — fetch a card via card.wb.ru/cards/v2/detail?nm=<id> if needed (that endpoint sometimes needs extra params).
Seller / analytics APIs (TOKEN required)
- Wildberries: header
Authorization: $WB_TOKEN. Hosts:statistics-api.wildberries.ru(sales detail/api/v5/supplier/reportDetailByPeriod),analytics-api.wildberries.ru(funnel, search queries, stock, item rating). ⚠️ WB has paid Pay-as-you-go access for external services. - Ozon: headers
Api-Key: $OZON_API_KEY+Client-Id: $OZON_CLIENT_ID, hostapi-seller.ozon.ru./v1/product/list,/v1/analytics/data. - Avito: OAuth
client_credentials→ bearer$AVITO_TOKEN, hostapi.avito.ru. Verticals include autoload, messenger, job, STR — confirm the current API version and vertical list against https://developers.avito.ru/ before calling (they change; the version at authoring time may already be stale).
⚠️ Verify before relying on any endpoint/param. The URLs, query params (
dest,nm), and auth headers below were captured at authoring time and are NOT guaranteed current. Confirm each against the live platform docs / DevTools before calling; never state an unconfirmed value to the user as fact.
How to work
- Clarify the goal: niche research (public WB), or the user's own sales/analytics (needs a token).
- For public research, use the WB v4 search; present top products + top brands as a table.
- For seller data, confirm the matching env var is set before calling; never log tokens.
- Caches over polling — analytics endpoints are rate-limited.
- Marketplace data is for research; respect each platform's terms — don't republish raw dumps.