Core concepts

Working with nodes

Nodes should be treated as reusable production steps. Keep source inputs explicit, connect only compatible socket types, and make important model parameters visible in the Inspector so a teammate can understand the workflow later.

Loops and variants

Use Loop when a branch already works and you want structured variants: camera angles, languages, products, seeds, durations, prompts, or model controls. Select a group, add iterations, then override only the fields that should change for each pass.

• Loop rows store overrides per node, so one node's seed or prompt does not leak into another node.
• Dynamic Camera derives the exact backend prompt from azimuth, elevation, and distance for every iteration.
• Disabled iterations are ignored during execution, which lets teams keep draft variants without deleting them.
• Rerun the loop node to apply loop settings; rerun an individual member only when you intentionally want an isolated run.

API keys

Users can manage personal API keys from /profile in the API Key tab. API keys use the mas_ prefix and authenticate as the key owner, so recipes, sessions, billing, media, and sharing permissions behave exactly like the web account.

Recipes API

Recipes create ready-made workflow sessions from validated input. They are the right integration point for templates, onboarding flows, and external systems that should open a prepared canvas for the user.

POST /api/v2/recipes/image_magic/run
Authorization: Bearer <token>
Content-Type: application/json

{
  "session_name": "Product hero variants",
  "execute": false,
  "inputs": {
    "source_image_url": "https://example.com/product.png",
    "edit_prompt": "premium studio lighting on a dark reflective surface",
    "negative_prompt": "blur, watermark, distorted logo",
    "seed": 0
  }
}

{
  "session_id": "72494ed2-73ad-4baa-9bf3-5f09a3efde7a"
}

Use execute: false when the user should inspect or edit the workflow first. Use execute: true only when all required inputs are final and the account is ready for GPU runtime.

Bundled recipes

Go SDK

The Go SDK is a small stdlib-only client for the Mini AI Studio /api/v2 API. Use it for server-side integrations, automation jobs, recipe-based onboarding, and internal tools that need to create sessions, run workflows, poll progress, and read outputs.

require miniaistudio-go-sdk v0.0.0

replace miniaistudio-go-sdk => ./miniaistudio

ctx := context.Background()
c := &miniaistudio.Client{APIKey: os.Getenv("MINIAI_API_KEY")}

created, err := c.CreateSessionFromRecipe(ctx, "prompt_to_avatar", map[string]any{
    "prompt": "a cinematic avatar portrait",
}, "Avatar workflow")
if err != nil {
    log.Fatal(err)
}

fmt.Println(created.SessionID)

run, err := c.RunRecipe(ctx, "prompt_to_avatar", miniaistudio.RunRecipeRequest{
    Inputs:  map[string]any{"prompt": "a portrait"},
    Execute: true,
})
if err != nil {
    log.Fatal(err)
}

raw, err := c.PollSession(ctx, run.SessionID, 2*time.Second, done)
outputs, err := miniaistudio.ParseExecutionOutputs(raw)
images := outputs.FlattenImages()

Media API

Media endpoints expose the same generated and uploaded assets shown in My Gallery and the dashboard gallery picker. Use media ids for downloads rather than raw URLs so access checks stay server-side.

Sharing API

Sharing is role-based. Viewers can inspect, runners can execute, and editors can modify the graph. Owners can set monthly or total credit limits for collaborators before inviting them.

Execution API

Execution endpoints operate on the active session. Send X-Session-ID and the authenticated bearer token. Backend errors include a stable code field so clients can localize messages without parsing English text.

GPU billing

GPU-heavy nodes require runtime. Mini AI Studio tracks active GPU sessions, elapsed paid time, task count, expiry, and estimated refund if the user stops early.

• Start GPU from the GPU Control node or let a GPU workflow request it during execution.
• Use the billing page for balance, GPU session history, invoices, and checkout top-ups.
• For large production runs, contact sales before running so capacity, runtime, and workflow shape can be planned.

Error codes

API errors include a stable code field when possible. Client applications should translate from that code and avoid parsing English message text.

Troubleshooting