> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/administration/usage-monitoring.md).

# Usage monitoring

See how your organization uses credits and compute.

Organization admins can see what their organization is using in **Settings**.

| Page              | What it shows                                                                                             |
| ----------------- | --------------------------------------------------------------------------------------------------------- |
| **Credit Usage**  | Credits used across your organization                                                                     |
| **Compute Usage** | Compute used by block runs, broken down by compute type, such as AWS Fargate, AWS SageMaker or Kubernetes |

**Credit Usage** isn't available for on-premises installs.

## How usage is recorded

Every call an agent makes to a model is recorded with the number of input and output tokens, the model and provider used, and the credits it cost. Usage is attributed to the conversation it belongs to and, for superagents, down to the individual team member and task. Every block run's compute is recorded too.

## Superagent usage

Each superagent's page shows its own spending: credits used today against its daily budget, and credits used in the last 24 hours. See [Budgets and credits](/zerve-docs/superagents/budgets-and-credits.md#tracking-spending).

## Understanding usage

For what uses credits, and how to keep usage down, see [How credits are used](/zerve-docs/administration/how-credits-are-used.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 by asking a question.

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

```
GET https://docs.zerve.ai/zerve-docs/administration/usage-monitoring.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.