About the service
The service assembles product card sets for marketplaces: it plans the slides, writes the copy, lays out the infographics and checks everything against the marketplace's requirements.
What the service does
A seller describes a product and picks a category. The service plans a card set, writes the copy, builds infographics from layouts, checks the slides against the marketplace's requirements, and delivers the finished set to the cabinet.
It runs on models: AI plans the set, writes the copy and produces the images. The result is probabilistic and needs checking before publication - that is not a disclaimer at the foot of a page but a property of the method.
How the pipeline is arranged
Five steps, each of which can be named.
- The planner receives the category, the marketplace and the product description, and returns a list of slides with roles.
- The copy assistants write the title, the description, the bullets and the keywords - after asking clarifying questions.
- The slides are built from layouts, with text placed into named zones.
- The quality gate compares the facts about each card with the marketplace's requirements and returns a specific discrepancy.
- Video and slideshows are assembled from the finished slides, on a queue of their own, because a render takes a whole core.
Where the prices come from
From the pricing engine, not from the text of a page.
The price of an operation is its tokens multiplied by the price of a token on your plan. The pricing engine holds both and raises the invoice; the pricing page reads it as the page opens, so the figure on the page and the figure on the invoice are one figure.
The cost of an operation is computed from the provider's price for the model, a currency buffer and a waste factor. That part is internal: only the price is published, but it is not set by hand.
What the service does not do
This is the current state rather than a roadmap, and it is better known in advance.
- There is no virtual try-on.
- There is no catalogue-wide batch processing.
- There is no public API with keys and documentation.
- Marketplace requirements are known for Wildberries and Ozon; for Yandex Market, Avito and Kaspi they are not.
How to reach us
The channels that exist and what to do about account questions are on the contact page.