Skip to main content
Credits are the unit of metered usage in VibeFlow. The canvas product bills both per-turn (for chat-driven generations) and per-action (for a few flat-rate tools).

​
Per-turn billing

A canvas chat turn is token-based with a one-credit minimum to start. The cost depends on:
  • The size of the brief and context (chat history, attached frames, design system, skills).
  • The amount of output the agent writes (frame HTML, narration).
  • The tools the agent calls in the turn (some have a small flat surcharge, see below).
The exact cost of the last turn shows in the chat right under the agent’s reply, so you can see what each action did to your balance. If your balance is below the minimum, the turn doesn’t start. You’ll see “insufficient credits” in chat and nothing is debited.

​
Per-action billing (flat rates)

A handful of canvas tools have a small flat cost on top of token usage, because they hit external services. Flat charges land in addition to the per-turn token cost.

​
Promote to app

The promote charge is for scaffolding the new project. Editing and deploying that project afterward bills against the UI product’s own meter (covered at docs.vibeflow.ai).

​
Server exports

PPTX, PDF, PNG, and JPG exports are not metered at the export step. They run against the project storage you’ve already paid for. There is no per-export cost. Client exports (HTML, React, Prompt) are obviously free; they run in your browser.

​
MCP usage

MCP tool calls bill identically to in-app usage. The agent runs via the same run_canvas_agent path and applies the same credit gates. Calling MCP tools doesn’t bypass anything. If a tool fails for reasons other than insufficient credits (a validator error, a 5xx from an underlying service), no credit is consumed.

​
Watching your balance

The canvas editor doesn’t show the balance widget inline (the chat shows per-turn cost instead). To see your balance: You can top up at any time. Top-ups apply instantly.

​
Plans

Plans, monthly allowances, and team seats are covered on the pricing page. Plans are shared across the canvas and UI products; you don’t buy separate buckets.

​
Next

MCP overview

Same billing, from your editor.