> For the complete documentation index, see [llms.txt](https://rakosell.gitbook.io/rakosell-setup-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rakosell.gitbook.io/rakosell-setup-tutorials/30-rakosells-billing-model.md).

# (30) Rakosell's Billing Model

Rakosell will charge users for service fees on the last day of each month, making it easier for you to manage your billing. To help you better understand this new billing model, we provide the following two examples:

**Example 1:**\
Suppose you purchase a Rakosell plan on January 1st. Regardless of whether you choose the basic or premium plan, we will charge you the service fee on January 31st. This means you will make your payment on the last day of each month to enjoy uninterrupted service.

**Example 2:**\
If you purchase a plan on January 29th, we will also charge you on January 31st. This allows you to start using our services immediately without having to wait until the first day of the next month.

This new billing model offers you greater flexibility, making it easier to keep track of your expenses.


---

# 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://rakosell.gitbook.io/rakosell-setup-tutorials/30-rakosells-billing-model.md?ask=<question>&goal=<endgoal>
```

`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.