Read your first project and result

This walkthrough reads the studio catalog and one existing project, then retrieves a material already in that project. It makes no project changes and starts no generations, so these calls incur no Vini generation charges.

You need a connected agent with a Look only (Только смотреть) key. An existing project is needed from step 3; an existing generated or uploaded image is needed for steps 4–5. The client itself may charge for its assistant conversation.

You can give your agent this request:

Use Vini MCP to describe the studio, list my projects, and read the project I choose. Explain its nodes and connections. Find an existing image in that project, let me choose it and retrieve its download link. Do not change anything or start a generation. Stop if there is no project or suitable image.

The examples below show MCP tool names and their arguments. Your client sends them as tool calls; they are not REST request bodies.

1. Read the studio catalog

{"name":"describe_studio","arguments":{}}

The response describes active node types, their purposes, inputs, outputs and public settings. It also includes image and video model information and pricing. This is the current catalog to use when discussing what the studio supports.

This call takes no arguments. Do not add a project, language or model filter.

2. Find a project

{"name":"list_projects","arguments":{}}

The response has a projects list. Entries include id, name, updated_at and workspace_id; a browser url is included when available.

Choose the intended project from this returned list. If there are several plausible matches, have the agent ask which one you mean. If projects is empty, the connection check has succeeded and there is no project to inspect: stop here. You can create a project in the studio and return to this guide later.

3. Read the chosen graph

Replace the placeholder below with that project’s returned url or id:

{"name":"read_project_graph","arguments":{"project_id":"<url or id returned by list_projects>"}}

The response identifies the project and its revision, then describes its nodes, connections and stage. A node can include its type, title, properties, stored result status and result kind. Connections identify the ports at both ends.

Have the agent explain where the idea enters, which nodes write text, which create media, and how the outputs connect. A newly created project may have an empty graph; that is a valid result.

Use the returned reference exactly. A project URL is not a public access link. If the project is unavailable, return to list_projects and check the account and selection instead of guessing another ID.

4. Find an existing result

Use the same project reference to list its images:

{"name":"list_artifacts","arguments":{"project_id":"<url or id returned by list_projects>","kind":"image","limit":20}}

Choose the intended material from the returned artifacts list, using its ID and project context. An uploaded image is also a valid material for this exercise. If several materials could match, have the agent ask which one you want.

If the list has no suitable image, stop the result-retrieval exercise. The list is bounded, so absence from it does not prove that the project never had an image. Check the project and intended kind before concluding that a result is missing. Do not create a new image merely to complete this walkthrough.

5. Retrieve and inspect the material

Use the ID you selected from that list:

{"name":"get_artifact","arguments":{"artifact_id":"<artifact id returned by list_artifacts>"}}

The response describes the material and, when it can issue one, provides download_url and expires_at. Open or download that exact link and inspect the image. Confirm it is the intended material, rather than treating a successful metadata response as proof you have the file.

The link lasts 15 minutes. If it expires, call get_artifact again for the same ID; do not repeat a generation. If no download link is returned, read download_note and follow its explanation. Keep the result’s visibility in mind when sharing a temporary link with someone else.

What you have verified

You have verified the connection, the account’s project list and, when they exist, the selected project’s graph and a retrievable material. The complete path ends with opening the actual file. You have not run the graph or established that this material matches the project’s latest inputs.

Keep identifiers and port names exactly as the tools return them, including Russian names. The agent can explain them in English without changing their spelling in tool arguments.

Continue with how the studio works or what agents can do. To create a new result, follow run a node: quote the work and agree its spending ceiling first. That is a separate paid-capable workflow.

Last checked: 14 October 2026. All five calls require reading permission only. The complete route is exercised against an isolated project with a prepared image: the test retrieves the file, checks its bytes and verifies that no graph, generation or billing record changed. This is a free fixture check, not a newly generated image or a claim that every version of every MCP client was launched.