> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/archive/guides-legacy/where-to-see-your-credits.md).

# Where to see your credits

You can easily see your credits by pressing the name of your app. Gray area is the credits you have in your monthly subscription and white area is the credits used.

#### Credit usage

Riff uses a usage-based credit system tied to the agent’s actual usage. Each message sent to the Riff agent deducts credits, with the amount determined by the complexity of the request. This ensures you pay only for what you use, making it highly cost-effective. As you may notice a lot of messages cost less than one credit, while more complex ones will cost you more.

#### Credits used on deployed apps

Additionally, credits are deducted when you have deployed apps. If the backend is running, which is that there are processes running in addition to the frontend being displayed, we charge 2 credits per hour. This is to cover the server cost the app is inflicting

<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.riff.ai/archive/guides-legacy/where-to-see-your-credits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.