Models

Many nodes generate their output with an AI model — image, video, text, and audio nodes all call a model under the hood. You choose which model a node uses, and that choice shapes what the node can do, which settings it exposes, and what it costs to run.

​

Families, variants, and tiers

Models are organized in three levels:

• Family — a related set of models from one provider that share an identity, like Flux, Veo, or Claude.
• Variant — a specific version you can select, like Flux 2 Pro or Veo 3 Fast. This is the thing you actually pick on a node.
• Tier — an optional quality or speed level within a variant. When a variant has tiers, picking a faster tier usually trades some quality for a lower cost, and vice versa.

​

Picking a model on a node

Select a node on the canvas to open its config panel, then choose the model from the model selector. Only models that can perform that node’s job are offered — a generate image node lists image models, a generate video node lists video models, and so on. When you switch models, two things change:

• Settings. Each model exposes its own set of settings. Switching to a different model can add, remove, or replace the fields in the config panel. See Model settings for what these controls do.
• Cost. The estimated credit cost updates to reflect the selected model, tier, and settings. You see the new estimate before you run the node.

​

Provider access and cost

You don’t supply provider API keys for these models. Pleyor routes each request to the provider and bills the work in credits, so you manage one balance instead of separate accounts and keys per provider. See Credits and billing for how cost is estimated, reserved, and settled.

​

Browse models by type