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

# Analytics

Admin Analytics show data about consumption, usage and configurations. Use it to analyse activity metrics over time.

### **Overview**

Analytics events are aggregated into hourly buckets ready for analysis. Deleted records are consolidated into "Deleted" rows so data-retention rules are always honoured, and where your organisation requires it, personal details such as user names and e-mail addresses can be obfuscated based on permissions.

Every row expands to reveal further detail, and reports only cover periods where activity was actually recorded.

### **Consumption**

Everything related to LLM consumption, grouped into the categories you already know from working in Blockbrain.

**Bots** — Filter and rank bots by compute blocks, active users and usage trend. Each bot also reveals its configuration, the models it has drawn on over time, model share by queries, and engagement metrics such as active users, conversations and messages.

**Users** — Model usage per user, measured both by consumption and by requests, and broken down by action, bot, API key or agent.

**Knowledge Bases** — Configuration details that explain what drove consumption, alongside ingest activity over time.

**LLMs** — Compute blocks, requests, and input and output tokens over time, with share attributed to bot, agent and action.

**Agents** — Model share by queries, plus compute blocks, requests and active users over time.

**Actions** — The detail adapts to the action itself: the agent or bot behind it, the knowledge base involved, and usage broken down over time.

**API Keys** — Usage per key, surfaced through whichever of the categories above reflects what the key has been used for.

### **Usage**

Statistics on invocations that don't necessarily consume tokens. Tools, MCP, Custom API and Skills each share the same view: invocation share by bot, by agent and by user, with matching breakdowns over time.

***

The biggest change is collapsing the four identical Usage subsections into one sentence — repeating the same two lines four times reads as an oversight. If your docs structure needs those four headings to exist separately for navigation, I can restore them with a pointer back to the shared description instead.


---

# 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.blockbrain.ai/for-admins/analytics.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.