What agents can do
An agent’s available tools depend on its Vini key. The list itself changes with the key’s permissions, so a read-only agent does not see tools for changing or generating content.
Choose the right permission
Section titled “Choose the right permission”| Key permission | Available work |
|---|---|
| Look only / Только смотреть | Inspect the catalog, projects, materials, runs and spending. |
| Look and build / Смотреть и собирать | Also create and organize projects, edit graphs and upload materials. |
| Look, build and generate / Смотреть, собирать и генерировать | Also start paid operations against the account balance. |
Building a graph does not generate its media. For a first connection check, use the read-only walkthrough.
Find the route for your task
Section titled “Find the route for your task”| Task | Agent route | Review or next step |
|---|---|---|
| Read an existing project | read_project_graph, then the relevant scene, Element or artifact tools. |
Follow the inspection guide. |
| Keep shared world and format rules | lore_standard → questions for the person → write_lore. |
Follow the lore standard; inspect the complete documents before generating. |
| Generate a supported branch of a graph | price_quote → run_node → get_run. |
The selected node and required upstream work must be supported. |
| Assemble explicit clips or decorate a finished film | assemble_video or decorate_video, then get_job. |
Follow individual media operations; this does not extend run_node support. |
| Reuse an episode’s saved decoration style | Read its design_profile with get_artifact, then pass it as series_profile to decorate_video with renderer: 'hyperframes' and decoration_version: 2. |
Read the series workflow, check warnings and review the new film. |
| Prepare a post for a connected social account | list_social_accounts → put_publish_draft. |
Open the returned open_url; a person reviews the publication form and confirms it. |
Running a node follows the graph
Section titled “Running a node follows the graph”run_node executes a selected node and the upstream work it needs. It saves results back to the project. The current path covers supported text work, scene images or storyboard sheets, and video generation.
The usual sequence is price_quote → run_node → get_run. The quote describes the current plan and estimate; a paid run needs a max_cost_usd ceiling. Use get_run until a terminal status is returned, then inspect the saved result.
up_to can reuse current results. regen regenerates the selected node and can charge again. Only one graph run can be active per owner; a busy response is a reason to wait, not to start more copies.
This path does not run Montage, Clip trim, Decoration or publication nodes. Music, voice and upscale nodes are also outside its current supported set. An unsupported node in the plan causes a refusal before the run starts.
Individual media tools are a separate path
Section titled “Individual media tools are a separate path”The MCP catalog also contains tools such as generate_music, generate_voice, upscale_image, assemble_video, edit_video and decorate_video. Their presence does not mean run_node supports the corresponding node.
These tools perform a particular operation with explicit parameters. Read the current tool contract for required inputs, cost and result handling. A queued generation returns a job to follow with get_job; a job being accepted is not the same as a finished file.
For assembly and decoration, keep the returned job identifier. After reconnecting, use list_jobs to locate existing work and get_job to follow it. A completed decoration returns artifact_id and a temporary download_url; retrieve the artifact and inspect the film before starting another paid operation. Repeating decorate_video with identical parameters while its job is still running joins that job; repeating it after completion starts a new paid decoration. See job recovery.
Work that stays in the studio
Section titled “Work that stays in the studio”Create and revoke API keys in the browser. Publication to connected social accounts also requires the person’s browser workflow. MCP does not provide a single command that runs an entire project from start to published video.
Preparing a post is available with build permission and costs $0. put_publish_draft saves one draft per platform in a project; a later draft replaces the previous one. It supplies the caption, account and applicable cover to the editable form, without publishing. YouTube uses the caption’s first line as its title and does not use the prepared cover frame. TikTok’s draft transfer carries only the video, so finish its text and settings in TikTok. See publish a finished video for both paths.
Project format is readable through MCP, but its project-wide setting is changed in the studio. Project links require the owning account; they do not grant editing access to a recipient.
Check outcomes and costs
Section titled “Check outcomes and costs”A failed or stopped run can still have submitted a vendor job. Stopping prevents new requests; it does not cancel payment for already submitted work. not_saved means the run’s result was not saved to the graph, even if work was charged. Follow the returned error and recovery instructions before retrying.
The API reference lists the tools and permissions. The agent operating guide describes quoting, cache recovery, pending jobs and run statuses in more detail.
Last checked: 22 October 2026. This is a boundary guide, not a paid-generation walkthrough; use the live catalog and quote for the particular work you intend to run.
