> For the complete documentation index, see [llms.txt](https://docs.buzzy.buzz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buzzy.buzz/working-with-buzzy/buzzy-ai/ai-tokens-and-pricing.md).

# AI usage and pricing

Choose how AI usage is funded when creating or editing Buzzy apps.

AI usage is separate from a Buzzy Deployment subscription. A Deployment runs and publishes your apps; it does not include a recurring monthly AI credit allowance.

You can use one of three AI-assisted creation paths.

## 1. Recommended: Buzzy Builder MCP

Use [Buzzy Builder MCP](/the-building-blocks/mcp/buzzy-builder-mcp.md) with an MCP-capable agentic AI development tool such as Codex, Claude Code, Cursor, or Antigravity.

The AI tool uses the subscription, usage allowance, billing, and terms attached to that tool or account. Whether you also need Buzzy AI generation credits or a supported bring-your-own OpenAI API key depends on whether you use Builder MCP to Create from scratch or Adapt an existing app.

### Builder MCP: Create vs Adapt

Builder MCP has two different cost paths:

* **Create from scratch:** when your agent asks Buzzy to generate a new brief, flows, data model, theme, blueprint, sample data, or screens, that Buzzy-managed generation requires separately purchased Buzzy AI credits or a supported bring-your-own OpenAI API key. Your agentic tool's own subscription or usage allowance also applies.
* **Adapt a template or existing app:** when your agent copies or inspects an existing Buzzy app and edits its artifacts directly inside Codex, Claude Code, Cursor, Antigravity, or another compatible agentic tool, Buzzy AI generation credits are not required. The agentic tool's own subscription or usage allowance still applies.

If you explicitly invoke a Buzzy generation tool during an Adapt workflow, the Create-generation requirements apply to that generated step.

{% hint style="success" %}
**Why Buzzy recommends this path:** in our experience, Builder MCP has often been the most cost-effective path and produced the best-quality results for serious app creation and editing, while supporting staged review and control. The agent works with Buzzy's structured app artifacts and can inspect, change, validate, and verify the app in stages.
{% endhint %}

## 2. Bring your own OpenAI API key

Supported Buzzy AI and Figma-plugin workflows can use your own OpenAI API key. OpenAI usage and charges run through your OpenAI account rather than Buzzy AI credits.

Keep the key private, restrict it where the provider supports restrictions, monitor its usage, and never paste it into a prompt, repository, screenshot, or public issue.

## 3. Purchase Buzzy AI credits

Purchase dollar-based Buzzy AI credits when you want to use Buzzy-managed AI for a particular generation or iteration workflow. Credits are purchased separately from Deployment subscriptions and are consumed according to the AI work requested.

Used Buzzy AI credits are non-refundable. See [Buzzy pricing](https://www.buzzy.buzz/pricing#purchase-ai-credits) for the current purchase option.

## Important limitations

AI cost and output quality vary with:

* what you are building or changing
* the clarity and completeness of your instructions
* the selected model
* the model's current performance and provider limits
* how much review, testing, and iteration the app requires

AI models can make mistakes. Review the app definition, permissions, workflows, screens, generated code, tests, and runtime behavior before publishing or using the app with production data.

## FAQ

### Does my Small, Medium, or Large Deployment include monthly AI credits?

No. Deployment subscriptions cover the infrastructure and publishing capabilities listed for the selected plan. Direct Builder MCP adaptation uses your agentic tool's allowance. Builder MCP Create workflows that invoke Buzzy generation also require a supported bring-your-own OpenAI API key or separately purchased Buzzy AI credits.

### Which path should I start with?

For most serious builds, start with [Buzzy Builder MCP](/the-building-blocks/mcp/buzzy-builder-mcp.md). Adapt a suitable template or existing app when possible; direct adaptation normally avoids Buzzy generation-credit usage. For a Create workflow from scratch, use a supported bring-your-own OpenAI API key or purchase Buzzy AI credits for Buzzy-managed generation.

### Are purchased Buzzy AI credits part of my agentic AI tool subscription?

No. They are separate. Your connected AI tool's account, usage allowance, billing, and terms apply to Builder MCP activity. Purchased Buzzy AI credits apply only when a workflow invokes Buzzy-managed generation.

### Does Builder MCP always avoid Buzzy AI credit usage?

No. Direct adaptation and editing do not require Buzzy AI generation credits. A Create workflow that uses Buzzy to generate new app artifacts, sample data, or screens requires separately purchased Buzzy AI credits or a supported bring-your-own OpenAI API key. See [Builder MCP: Create vs Adapt](#builder-mcp-create-vs-adapt).

### Can I create or edit without AI?

Yes. You can use Buzzy's no-code Workspace and the Buzzy Figma plugin manually without using AI credits.

### Can I cancel a Deployment subscription?

Yes. You can cancel a paid Deployment subscription at any time. Before contacting Buzzy Support, confirm that the receipt or invoice is identified as `BUZZY.BUZZ`.

For a `BUZZY.BUZZ` subscription, see [how to cancel a Buzzy subscription](/working-with-buzzy/buzzy-ai/troubleshooting-buzzy-ai.md#cancel-a-subscription) and review the [cancellation and refund policy](https://www.buzzy.buzz/cancellations).