> For the complete documentation index, see [llms.txt](https://docs.graspil.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graspil.com/en/other/pricing.md). # Pricing We strive to make our pricing system as transparent and predictable as possible. Our billing works on a **prepaid balance** model with daily charges. You don't need to pay a month in advance for resources you don't plan to use. In this article, we'll explain in detail how resources are tracked, how limits work, and how charges are applied. Current plan and resource prices are always available on our website. ### General concept Your account has a single balance, which you can top up using any convenient method (bank cards, cryptocurrency). **Every night**, the system deducts a small amount from your balance — the cost of your plan and the resources used over the past day. This approach allows you to: * **Pay only for what you use.** You can change your plan at any time, and charges will automatically be recalculated starting the next day. * **Avoid surprises.** You always see your current balance, charge history, and a forecast of expenses through the end of the month. *** ### Free plan The Free plan is designed so you can test the platform or use it for small projects. The plan includes a certain monthly resource limit. If your bots start growing and exceed these free limits, we do **not** start charging for the overage. Instead: 1. The system stops collecting/accepting data. 2. You receive a notification via email and Telegram. 3. To resume operation, you'll be prompted to switch to a paid plan (Premium). *Your data and sessions are preserved, so after switching to Premium your bots will continue working seamlessly.* *** ### Paid plan and resource tracking When you switch to Premium, you pay the base cost of the plan. This cost already includes a certain package of resources. We only charge for four main metrics: 1. **Events** — all incoming messages and user interactions with your bots. Automation runs and broadcasts are not included here. 2. **Broadcasting** — the number of messages sent through the mass broadcast functionality. 3. **Automation** — the number of workflow runs (automation scenarios). 4. **Storage** — the amount of data occupied by your bots' message history. #### Progressive pricing (Overage) If you exceed the amount of resources included in your base plan, you don't need to purchase a more expensive plan entirely. You simply pay for the overage as it occurs. We use a **progressive (tiered) pricing scale**. This means that the more resources you use above the limit, the cheaper each additional unit becomes. > **Example:** Suppose your plan includes 500,000 events. If you used 600,000, the first 500,000 are already covered by your plan, and you pay the first (base) overage rate for the remaining 100,000. If you grow to several million events, the cost of each subsequent million decreases proportionally. *** ### How exactly are charges applied? Daily charges are structured to distribute the financial load as evenly as possible throughout the month: 1. **Base plan cost.** Every night the system divides the monthly cost of your plan by the number of days in the current month and deducts that small portion. 2. **Overage payment.** The system takes all your overage since the start of the current month, calculates its full cost using the progressive scale, and then also divides that amount by the number of days in the month. *This way, payment for over-limit usage is "spread out" across days rather than charged as a one-time payment at the moment the limit is exceeded.* All charges are broken down in detail. In the transaction history you can always see the breakdown: how much was charged for the plan itself, and how much for each resource category. *** ### Auto-recharge and balance control To make sure your resources don't stop due to a zero balance, the system provides convenient control tools: * **Low balance notifications.** You can set a threshold, and when it's reached we'll send you a warning. * **Auto-recharge.** When paying by bank card, you can enable auto-recharge. You set: * *Trigger threshold* — the balance level at which to initiate a payment. * *Recharge amount* — how much money to charge from the card at one time. * *Monthly limit* — the maximum amount of auto-charges per month. This is your guarantee against unexpected expenses: if the limit is reached, the system won't charge your card a single cent more until a new calendar month begins. *** ### Transparency and forecasts In the billing dashboard, you always have access to: * **Current statistics** on resource usage since the start of the month. * **Forecast through the end of the month** — the system projects your current activity and shows the expected amount your platform usage will cost this month, if consumption rates don't change. ### How to optimize expenses? How to optimize expenses is described in the [next article](/en/other/pricing/optimization.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.graspil.com/en/other/pricing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.