Skip to main content

Pricing

Every model and tool Flowera supports has a published rate. You can read the whole list inside the product: Usage Dashboard → Pricing.

The Pricing tab of the Usage Dashboard, listing every model with its input, output, voice, and execution rates.

How to read the price table​

The table has one row per model or tool, and the columns are the different ways something can be charged:

ColumnUnitApplies to
InputPer 1M tokensText sent to the model
OutputPer 1M tokensText the model generates
VoicePer minuteSpeech-to-text and text-to-speech
ExecPer minuteWall-clock time the node runs
RequestPer callTools charged per invocation rather than per token

A dash means that column doesn't apply — most chat models have no voice rate, most tools have no token rate.

Search by model or provider, and filter by Node Type or Provider, to find the row you care about. The counter above the table tells you how many entries match.

Making sense of the numbers​

Per-million-token prices are hard to feel. A rough translation:

  • A typical support exchange — a system prompt, a few turns of history, a retrieved passage, and a short reply — is on the order of 2,000 input and 200 output tokens.
  • At $4.00 per 1M input and $16.00 per 1M output — the rate for gpt-4.1-mini — that's about $0.011 per message.
  • At $75 / $375 — the rate for a flagship like claude-opus-4-1 — the same exchange is about $0.23, roughly 20× more.

The rates in the Pricing tab are the rates you are charged. There is no markup to add on top and no separate provider bill.

Neither is expensive on its own. The difference shows up at ten thousand messages a month, which is why choosing the right model per node is the single most effective cost decision you make.

Which node produces which cost​

NodeCharges
LLM, Agent, Condition Agent, Human InputInput and output tokens, plus execution time
RetrieverEmbedding tokens for the query, plus execution time
Tool, HTTPPer-request charges where they apply, plus execution time
Condition, Filter, Direct ReplyA small token charge estimated from the text they handle, plus execution time
WaitThe wait duration itself, at its own low per-second rate

Every node accrues execution time, including the ones that don't call a model. It's small per node, and it adds up on flows with many steps.

Why the same model differs by provider​

The same model name can appear under more than one provider — through Azure, through an aggregator like OpenRouter, or direct. Each has its own row because each charges differently. Where a model appears more than once, check which provider your node is actually set to.

Using your own provider key​

You can attach your own provider credential to a node — for a model Flowera doesn't hold a key for, for a rate you've negotiated directly, or to keep usage on your own provider account for your own reporting.

Your own key does not reduce your Flowera bill

Flowera meters token usage from the model's response, not from whose key produced it. With your own credential attached you are billed twice: once by your provider, and once from your Flowera wallet at the rate in the Pricing tab. Bring your own key when you need the account, not to save money.

How prices are updated​

Prices change only when the seed CSV changes and the app is redeployed. The product and this table read the same file, so there is no separate price list that can drift out of sync — and no price can change while the app is running.

The Pricing tab is always the authoritative version for your installation. If a number here and a number there ever disagree, the product is right.