> ## Documentation Index > Fetch the complete documentation index at: https://docs.canvasview.dev/llms.txt > Use this file to discover all available pages before exploring further. # Credits and billing > What CanvasView charges for, what is free, how the daily spending cap works, and how to add credits. CanvasView runs on prepaid credits. They pay for creating and changing canvases, and for runs of each [canvas's agent](https://docs.canvasview.dev/people/canvas-agent.md). Everything else is free. > [!NOTE] > > Prices are not final. This page describes how charging works. For current prices, see your [Billing](https://app.canvasview.dev/settings/billing) page or the pricing line in [llms.txt](https://app.canvasview.dev/llms.txt). ## What is charged | Action | Charge | | - | - | | Create a canvas (`create_canvas`) | A charge for each canvas. | | Update a canvas (`update_canvas`, or `patch_canvas` with structural changes) | Each canvas includes a number of updates at no extra charge. Each update after those has a small charge. | | Patch that only changes data on existing components | Free. It does not use an included update. | | A run of the canvas's agent | Its model use, up to \$0.25 a run. Each change it makes to the canvas is charged like an update. | A patch costs one update however many operations it holds. Retrying a request with the same idempotency key returns the first result and charges once. ## What is free * Checking a canvas before creating it (`validate_canvas`), which also returns the price. * Reading canvases, answers, events, comments and notifications. * Arranging a canvas, and changing its access, expiry, keep setting or deleting it. * Shared state, examples, and saving or searching templates and components. Creating a canvas from a template is charged as a create. * Everything people do on a canvas: opening it, working on it, commenting and answering. Asking the canvas's agent is charged as above. * Calls that components make to your [data sources](https://docs.canvasview.dev/account/data-sources.md), and, for now, running canvas tools. ## Who can manage billing Credits belong to the organization, and every member's agents spend from the same balance. Only Admins can add credits, change the daily spend cap, set key caps and see recent activity. Members do not see the Billing page. They see **Available credits** on the API keys page and can ask an Admin to add credits. See [Organizations and members](https://docs.canvasview.dev/account/organizations-and-members.md#roles). ## Your balance For Admins, the [Billing](https://app.canvasview.dev/settings/billing) page shows: * **Credit balance.** What you can spend now. An amount shown as reserved for requests in progress is held while a paid request runs, then settled. * **Add credits.** Buy credits through Stripe Checkout. * **Daily spend cap.** The most your account can spend in a day. * **Recent activity.** Refills, daily usage, and any credits added, removed, expired or reversed. The API keys page also shows **Available credits**. Your agent can read the balance with `get_balance`. ## Add credits 1. Open [Billing](https://app.canvasview.dev/settings/billing). 2. Under **Add credits**, enter a refill amount, from $5 to $500. 3. Select **Continue to Stripe** and complete the payment. Credits appear after Stripe confirms the payment. Purchased credits do not expire. Credits CanvasView adds, rather than ones you buy, can expire. Expired credits show as **Credits expired** in Recent activity. ## New accounts New accounts join a waitlist. After you sign up, CanvasView asks what you want to use it for and how many credits you think you need for testing: $5, $50, $500 or $5,000. The amount is a request, not a guarantee. CanvasView reviews each account and emails you when yours is approved, with any credit it added. Until then the workspace stays closed, you cannot buy credits, and your agent can only read examples, skills and the kit reference, validate a canvas and read the balance. After approval you connect your agent, or skip that step, and the workspace opens. Once the account is open, an Admin can add credits at any time. Only the person who created the organization sees these steps. People who join later skip them. ## Daily spending cap The daily cap limits what your organization spends each day. Days run from midnight to midnight UTC. Once the day's spending reaches the cap, paid requests fail with `spend_cap` until the next day. Free actions keep working. To change the cap: 1. Open [Billing](https://app.canvasview.dev/settings/billing). 2. Under **Daily spend cap**, enter an amount. 3. Select **Save**. The cap starts at $25 a day and can be up to $500. Set it to 0 to stop all paid requests. Runs of the canvas's agent count toward it. An Admin can also cap a single key or connected agent. On the [API keys](https://app.canvasview.dev/settings/keys) page, enter a **Daily cap (USD)**, up to \$500, next to the key and select **Save key cap**. Leave it empty for no key cap. The organization's cap still applies. Runs of the canvas's agent belong to no key, so key caps do not limit them. ## Billing emails CanvasView sends a billing email when the organization's spending reaches 80% of the daily cap, and when its balance falls below zero. ## When a request is refused | Error | What to do | | - | - | | `insufficient_credits` | Add credits, or ask an Admin to. | | `spend_cap` | Wait for the next UTC day, or ask an Admin to raise the organization or key cap. | | `payment_disputed` | A payment on the account is under dispute. Paid requests pause until it closes. Contact [support@canvasview.dev](mailto:support@canvasview.dev). | The full list of error codes is in the [error reference](https://app.canvasview.dev/agents/errors.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.