All Solistra integrations

Where to connect

All connections live in the Integrations section, reachable from the profile menu, from Cards and from clip publishing. Every connection lists what Solistra may do, and all actions are written to a log.

Wildberries and Ozon

Solistra works with Wildberries and Ozon directly through their seller APIs. Wildberries needs a WB API token with the Content category, Ozon needs a Client-Id and Api-Key with a product role.

Marketplace permissions are finding cards by SKU, uploading photos to cards and downloading photos from cards. Card videos, prices, stock and descriptions are never touched. Every write is verified by reading the card back, and previous photos can be restored from the log.

Downloading photos from cards

The integration works in the other direction too. Card photos download to the Solistra library in original quality with order and main photo preserved, or as one archive. Filters help find cards without video or with few photos.

The Improve as series button sends selected cards to Photo Studio, and after editing the photos go back into the same cards.

VK, YouTube and Telegram

Finished clips and videos are published from Solistra to video platforms.

• VK Video and Clips · video and clip upload, scheduled publishing, view stats
• YouTube · Shorts and video upload, view stats, sign in with a Google account
• Telegram · posting to channels where the Solistra bot is an admin
• Dzen and RuTube · a finished file for manual upload

Storage

Yandex Disk and Cloud Mail connect for source files. Solistra gets access to a chosen folder and takes long videos for clip cutting and files for processing from there, without manual browser uploads.

Solistra API

The Solistra API runs generations from your scripts, CRM or inventory system. An API key acts on your behalf and spends credits only within your balance. Webhooks tell your system when a result is ready.

The API is a convenient way to link Solistra with your own product system: a new catalog item triggers photos and video, and the result comes back into your system.

MCP for Claude

MCP is an open protocol that lets AI applications connect to external services. Your own Claude connects to Solistra over MCP from Claude Desktop, Claude Code or claude.ai with OAuth sign in.

In Motion, Claude assembles a video from scenes, text and music while the preview updates live. Access is granted with checkboxes, you set a daily spending limit, and publishing is off by default.

Tsiolkovsky for automation

Tsiolkovsky is a builder where an agent turns your description into an app made of image and video models, Photo Studio, voiceover, subtitles, clips and integrations with WB, Ozon, VK and Telegram. Apps run from a button, on a schedule, from a Telegram bot or via API.

Examples include cards by SKU for a new delivery, clips on a schedule and stories for a sale. The agent asks before every paid step, and per app and daily limits apply.

Connection security

Keys and tokens are encrypted and stored only on a server in Russia, never in the browser or logs. Disconnecting deletes the key. Where a platform supports OAuth sign in, Solistra uses it instead of keys. Publishing and writes run through a queue with platform limits, retries and result checks.