Return a cheat-sheet of every filter code this server understands, how values are encoded, and which tool resolves names to ids. Call this once at the start of a browsing session instead of guessing filter names.

Search the oskelly.ru luxury marketplace catalog and return matching product cards (id, brand, category, price, discount, condition, in-stock sizes, seller, image, URL). Supports full-text query, faceted filtering (brand, category, size, condition, collection, model, seller type, boutique, price range, boolean tags such as sale/vintage/outlet), pagination and sorting. Use oskelly_search_facets first when you need to know which filter values are available, and oskelly_filter_values to resolve names to ids.

Run the same search as oskelly_search_products but return the total result count plus the list of facets available for that result set (their codes, names, types, hot values and the price range present) instead of the products. Use this to discover which filters make sense before drilling down, or to count matches cheaply without fetching items.

List the selectable values (with their ids) of a single facet, scoped to the same search context. This is how you resolve a human name to the numeric id that oskelly_search_products expects — e.g. code='brand' to find the id of GUCCI, code='size' to find size value ids for the current category. Accepts every search parameter so the returned values reflect the narrowed result set.

Get search-query autocomplete suggestions from oskelly.ru for a partial user query. Useful for discovering how the marketplace phrases things (brand + item combinations) before running a full search.

Return the oskelly.ru category tree. The root (id 1, 'Каталог') has the four top-level segments as children — their ids are real tree node ids read from the live tree, not a fixed enum. Use rootId to zoom into a subtree and depth to control how many levels come back (the full tree is ~618 nodes / 1 MB, so keep depth small). Category ids from here feed oskelly_search_products categoryIds and baseCategory.

List brands available on oskelly.ru with their numeric ids (needed for the brandIds search filter), url slugs and transliterated Russian names. The full list is ~7000 brands, so filter with nameContains or page through with limit/offset.

List the product condition grades used on oskelly.ru (id, name and the full Russian explanation of what each grade guarantees). Condition ids feed the conditionIds filter.

List the product attribute dictionary (material, colour, style, ... ) with every possible value and its id. These are the attributes shown on a product card as 'Материал', 'Цвет' etc. Filter by name/code to keep the response small.

Fetch the full detail of a single oskelly.ru product by numeric id or product URL: description, condition, all attributes (material/colour/...), full size chart with per-size stock and pricing, breadcrumbs, every image, tags, and the seller's public profile. NOTE: oskelly.ru has no public JSON endpoint for a single product (/api/v2/products/{id} returns 404), so this reads the server-rendered Nuxt payload embedded in the product page and decodes it with the official devalue library.

List the products currently offered by a specific oskelly.ru seller (boutique, brand or private seller), with pagination and sorting. Seller ids come from the seller block of any product card or from oskelly_get_product.

Return the sets of ids that actually occur in one seller's inventory — which attribute values, categories, brands, sizes and conditions they carry. Use it to understand a seller's assortment before filtering their catalog.

Return the promotional banners / curated selections shown on the oskelly.ru homepage for a given audience segment: title, description, image, and the catalog link that opens the underlying selection. Feed a banner's catalogLink into oskelly_banner_catalog to see what products it actually resolves to.

Open an oskelly.ru curated-selection page (a banner's catalogLink, e.g. https://oskelly.ru/catalog/bannerV2/) and return its title, the filter preset it encodes (for example a specific seller's wardrobe), the total item count and the first page of products. Curated pages are rendered server-side, so this reads the page's Nuxt payload rather than an API endpoint.