> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lyzr.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage Pricing

> Consumption-based pricing - one price per run, set by complexity. No feature gates, no seat counts, no hidden charges.

Lyzr runs on a **consumption-based model**. You pay only for the agents you run - no per-seat fees, no feature gates, no surprise charges. The same rates apply whether you ship one agent or a thousand.

<CardGroup cols={4}>
  <Card title="Model" icon="gauge">
    Consumption-based
  </Card>

  <Card title="Billing Unit" icon="coins">
    Credits per run
  </Card>

  <Card title="Transparency" icon="eye">
    No feature gates
  </Card>

  <Card title="LLM Costs" icon="arrow-right-arrow-left">
    Pass-through, no markup
  </Card>
</CardGroup>

<Note>
  Looking for subscription tiers and credit allocations instead? See [Plans & Credits](/enterprise/agent-studio/plans) and [Understanding Credits](/enterprise/get-started/credits). This page covers **how each run is priced**.
</Note>

***

## How it works

<Steps>
  <Step title="Purchase a subscription">
    Choose a plan that matches your expected volume. Your subscription converts directly into usable credits.
  </Step>

  <Step title="Receive credits">
    Credits sit in your workspace, ready to spend. No feature licenses to manage.
  </Step>

  <Step title="Run agents, deduct credits">
    Credits are deducted each time an agent runs. Cost reflects the work delivered, not the feature surface.
  </Step>
</Steps>

Three principles hold across every plan:

* **No feature gates** - every capability is included.
* **No hidden charges** - you pay for runs and complexity, nothing else.
* **Predictable cost** - one price per run, set by complexity tier.

<Note>
  **All prices are in USD.** Billing runs on credits where **1 credit = \$1**, so a \$0.06 run deducts 0.06 credits from your workspace. The same per-run prices apply whether you ship one agent or a thousand.
</Note>

***

## What counts as a run

A run is **one complete execution from input to output**. Whether a user types a question or a scheduled workflow fires at 9 AM, each distinct execution is one run. A run is never priced by the number of agents involved, tools called, or features active - only by the complexity tier the agent belongs to.

A run is tied to a **request**, not a session. Each message a user sends is a new run - even if it's to the same agent, in the same conversation.

**Example - same agent, same chat, 2 runs:**

> 1. "Find the quarterly report" - 1 run - \$0.06
> 2. "Also break down revenue by department" - 1 run - \$0.06
>
> **Total: 2 runs, \$0.12**

What doesn't add to the run count: the internal work the agent does to fulfill a single request. If an agent fetches data, reasons across it, and formats a response - that is still one run. The counter increments when the user sends a new request, not when the agent takes another step.

These do **not** change the run count:

* Multiple agents working together - still one run.
* Multiple tool calls within a workflow - still one run.
* Memory, knowledge bases, or integrations active - still one run.

<Note>
  **Included in every run at no extra cost:** memory, knowledge bases, semantic models, tool calls and integrations, and orchestration. There are no feature-level charges - the run price is all-in. The only separate line item is LLM tokens (see below).
</Note>

***

## The pricing equation

Two inputs decide your cost. Nothing else moves the number.

> **Agent Runs x Complexity = Your bill**

That's the whole formula. No per-agent fees. No per-seat fees. No feature add-ons.

<CardGroup cols={2}>
  <Card title="Agent Runs" icon="play">
    A **run** is a single execution request - regardless of how many agents participate in fulfilling it. One request means one run, whether it touches one agent or twenty.
  </Card>

  <Card title="Agent Complexity" icon="layer-group">
    Not all agents are priced the same. A single-agent task costs less than multi-agent orchestration; voice is priced separately. Complexity reflects the **nature of the work**, not the number of features used.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Daily Email Digest Agent" icon="envelope">
    A single agent runs every morning at 9 AM, scans your inbox, and sends a Slack message if something needs attention. One scheduled trigger = one run.

    **1 run/day x \$0.06 = \$0.06/day** *(SaaS, Simple)*
  </Card>

  <Card title="Research Assistant" icon="magnifying-glass">
    A manager coordinates three specialist agents to research a topic and return one brief. One request is one run, no matter how many agents run inside it.

    **500 runs/day x \$0.18 = \$90/day** *(SaaS, Intermediate)*
  </Card>

  <Card title="Patient Intake Workflow" icon="hospital">
    A form submission triggers a 6-node Superflow: parse the form, extract information, check the database, create or update the record. One submission = one run.

    **1,000 patients/day x \$0.30 = \$300/day** *(SaaS, Complex)*
  </Card>

  <Card title="Support Voice Line" icon="phone">
    An inbound voice agent handles a call. Voice is billed per minute of conversation, not per run.

    **5-minute call x \$0.09 = \$0.45 per call** *(SaaS, Voice)*
  </Card>
</CardGroup>

***

## Price at a glance

Pick the tier that matches the agent type you're building. The tier is visible when you configure the agent in Lyzr Studio. Pricing is shown for both deployment models - switch tabs to compare.

<CardGroup cols={2}>
  <Card title="SaaS" icon="cloud">
    Lyzr-hosted in the cloud. Start immediately - nothing to deploy or maintain. If you signed up at studio.lyzr.ai, you're on SaaS.
  </Card>

  <Card title="Customer VPC (On-Prem)" icon="building-lock">
    Lyzr deployed inside your own cloud or data center, so data and compute stay in your environment. Set up under an enterprise agreement.
  </Card>
</CardGroup>

<Tabs>
  <Tab title="SaaS">
    | Tier             | Agent Type    | Price               |
    | ---------------- | ------------- | ------------------- |
    | **Simple**       | Single Agent  | **\$0.06** / run    |
    | **Intermediate** | Manager Agent | **\$0.18** / run    |
    | **Complex**      | Superflow     | **\$0.30** / run    |
    | **Voice**        | Voice Agent   | **\$0.09** / minute |
  </Tab>

  <Tab title="Customer VPC (On-Prem)">
    | Tier             | Agent Type    | Price               |
    | ---------------- | ------------- | ------------------- |
    | **Simple**       | Single Agent  | **\$0.03** / run    |
    | **Intermediate** | Manager Agent | **\$0.09** / run    |
    | **Complex**      | Superflow     | **\$0.18** / run    |
    | **Voice**        | Voice Agent   | **\$0.06** / minute |
  </Tab>
</Tabs>

<Note>
  LLM tokens are billed separately as **pass-through at cost** - see [LLM costs](#llm-costs-pass-through-only) below.
</Note>

***

## Agent types & pricing

Each tier maps to an agent type you build in Studio. Start with the concept, follow the link to learn how to build it, and open **"Pricing for extreme cases"** only if you're running unusually heavy workloads.

### Simple - Single Agent

One agent handles the task end to end.

**When to use:** customer support replies, document summaries, ticket classification, one-shot data extraction.

| SaaS         | Customer VPC |
| ------------ | ------------ |
| \$0.06 / run | \$0.03 / run |

<Card title="Build a Single Agent" icon="robot" href="/enterprise/agent-studio/agents/studio">
  Learn how to configure and deploy a single agent in Lyzr Studio.
</Card>

### Intermediate - Manager Agent

Multiple agents coordinated by a manager. Best for branching workflows, multi-source research, and parallel tasks with a small team of specialist agents.

| SaaS         | Customer VPC |
| ------------ | ------------ |
| \$0.18 / run | \$0.09 / run |

<Card title="Build a Manager Agent" icon="sitemap" href="/enterprise/agent-studio/manageragent/studio">
  Learn how to orchestrate multiple agents with a manager.
</Card>

<AccordionGroup>
  <Accordion title="Pricing for extreme cases - many sub-agents" icon="layer-group">
    Manager pricing is based on the number of **sub-agents actually executed at runtime**, not the total number configured. Most managers fall in the base band; very large teams are priced in steps.

    | Sub-agents executed | SaaS   | Customer VPC |
    | ------------------- | ------ | ------------ |
    | 1-4                 | \$0.18 | \$0.09       |
    | 5-8                 | \$0.36 | \$0.18       |
    | 9 or more           | \$0.54 | \$0.27       |

    **Example:** a manager configured with 10 agents but only **4 executed** falls in the first band, billed at **\$0.09** (Customer VPC). The standard Manager price (\$0.18 SaaS / \$0.09 VPC) is exactly this first band - bands only step up beyond 4 executed sub-agents.
  </Accordion>
</AccordionGroup>

### Complex - Superflow

Multi-step orchestration across an agent network. Best for long-running business processes, multi-stage pipelines, and large agent networks.

| SaaS         | Customer VPC |
| ------------ | ------------ |
| \$0.30 / run | \$0.18 / run |

<Card title="Build a Superflow" icon="diagram-project" href="/enterprise/agent-studio/superflow/overview">
  Learn how to design multi-step orchestration with Superflow.
</Card>

<AccordionGroup>
  <Accordion title="Pricing for extreme cases - node-heavy & nested Superflows" icon="diagram-project">
    A standard Superflow falls in the base band. Pricing scales only when a flow runs an unusually large number of node executions.

    | Nodes executed | SaaS   | Customer VPC |
    | -------------- | ------ | ------------ |
    | 1-10           | \$0.30 | \$0.18       |
    | 11-20          | \$0.60 | \$0.36       |
    | 21-30          | \$0.90 | \$0.54       |

    **Beyond 30 node executions**, pricing switches to a per-node model on top of the 30-node band:

    | Deployment   | Cost per node (beyond 30) |
    | ------------ | ------------------------- |
    | SaaS         | \$0.02                    |
    | Customer VPC | \$0.01                    |

    **Example (Customer VPC):** 50 node executions = the 30-node band (\$0.54) + 20 extra nodes x \$0.01 = **\$0.74**.

    The node count includes loops, retries, dynamic branching, and any Superflow node. If you run multiple sub-tasks through **Spawns**, each sub-task counts as one executed node.

    **Nested Superflows:** when a Superflow invokes another Superflow, pricing accumulates across executions. For example, a parent at \$0.18 calling a nested flow at \$0.18 totals **\$0.36**; three Superflows executing would total **\$0.54** (Customer VPC).

    **Agent Swarms:** very large agent swarms are also priced separately - [reach out](https://www.lyzr.ai/book-demo) for a tailored quote.
  </Accordion>
</AccordionGroup>

### Voice - Voice Agent

Conversational voice interaction. Best for inbound and outbound calls, conversational IVR, and voice-driven customer journeys. Voice is billed **per minute**, not per run.

| SaaS            | Customer VPC    |
| --------------- | --------------- |
| \$0.09 / minute | \$0.06 / minute |

<Card title="Build a Voice Agent" icon="microphone" href="/enterprise/agent-studio/voice/overview">
  Learn how to configure and deploy a voice agent.
</Card>

***

## LLM costs - pass-through only

Lyzr does not mark up LLM usage. You either bring your own model and pay the provider directly, or use a Lyzr-provided model at exact cost.

<CardGroup cols={2}>
  <Card title="Bring your own model" icon="key">
    No LLM charges from Lyzr. You pay your model provider directly - those costs never touch your Lyzr credits.

    * Use your existing model contracts and pricing.
    * No LLM costs incurred from Lyzr.
    * Switch providers without touching your Lyzr bill.
  </Card>

  <Card title="Use a Lyzr-provided model" icon="server">
    Pass-through at cost, zero markup. If a model costs Lyzr one dollar, exactly one dollar is deducted from your credits.

    * One vendor, one bill - orchestration and tokens together.
    * Provider-rate pricing surfaced transparently in usage logs.
    * Switch between BYOM and Lyzr-provided per agent.
  </Card>
</CardGroup>

***

## Understanding your bill

Your billing view is designed to be understandable within minutes - no need to understand internal architecture or perform month-end reconciliation. For any agent you can see its complexity, run cost, deployment type, estimated monthly spend, and a clear split between platform cost and LLM cost.

<Card title="Example - Manager Agent on Customer VPC" icon="calculator">
  |               |                   |
  | ------------- | ----------------- |
  | Rate          | \$0.09 per run    |
  | Volume        | 10,000 runs/month |
  | Platform cost | **\$900**         |
  | LLM cost      | **\$400**         |
  | **Total**     | **\$1,300**       |
</Card>

***

## Common questions

<AccordionGroup>
  <Accordion title="Do I get charged per agent in a multi-agent workflow?">
    No. A workflow triggered by a single request counts as one run, regardless of how many agents execute within it.
  </Accordion>

  <Accordion title="What if my workflow runs on a schedule and no user is involved?">
    Scheduled executions count as runs too. Each time the workflow fires, it is one run.
  </Accordion>

  <Accordion title="Does using memory, knowledge bases, or integrations cost extra?">
    No. Features like memory, KB lookups, and tool integrations are included in the run - there are no feature-level charges.
  </Accordion>

  <Accordion title="What happens if I bring my own LLM?">
    Lyzr does not charge for LLM usage. You pay your model provider directly, and those costs don't touch your Lyzr credits.
  </Accordion>

  <Accordion title="How do I know which complexity tier my agent falls under?">
    The tier is determined by the agent type you build - Single, Manager, Superflow, or Voice. It's visible when you configure the agent in Lyzr Studio.
  </Accordion>

  <Accordion title="Are there any edge cases where pricing differs?">
    Yes. Very high-intensity scenarios - Superflows running large node counts (e.g. 1,000+ iteration loops), nested Superflows, or managers coordinating 9+ sub-agents - are priced in steps to cover the additional cost. See the **"Pricing for extreme cases"** sections above, or [talk to us](https://www.lyzr.ai/book-demo) for extreme scale.
  </Accordion>
</AccordionGroup>

***

## Start building

<CardGroup cols={2}>
  <Card title="Start with Lyzr Studio" icon="rocket" href="https://studio.lyzr.ai">
    Open a workspace and see the consumption model in action.
  </Card>

  <Card title="Talk to us" icon="comments" href="https://www.lyzr.ai/book-demo">
    Get a tailored credit plan for your expected volume or extreme-scale needs.
  </Card>
</CardGroup>