> For the complete documentation index, see [llms.txt](https://celopg.gitbook.io/tokenmanager/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://celopg.gitbook.io/tokenmanager/infrastructure/admin-dashboard.md).

# Admin Dashboard

React dashboard for platform analytics.

## Features

* **Analytics** — all tokens created (from the subgraph), per-token metrics, global stats, top-token ranking

{% hint style="info" %}
Holder/transfer/bridge metrics are currently **mocked** (derived deterministically from the token address) — not yet in the subgraph.
{% endhint %}

## Run

```bash
# Backend must be running first
cd admin
npm install
cp .env.example .env
npm run dev   # http://localhost:5174
```

| Env variable         | Purpose                                       |
| -------------------- | --------------------------------------------- |
| `VITE_API_URL`       | Backend URL (default `http://localhost:3001`) |
| `VITE_ADMIN_API_KEY` | Must match backend's `ADMIN_API_KEY`          |

Uses the `/api/admin/*` endpoints (see [Backend](/tokenmanager/infrastructure/backend.md)). Stack: React 19, TypeScript, Vite, TailwindCSS, Radix UI, TanStack Query.


---

# 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:

```
GET https://celopg.gitbook.io/tokenmanager/infrastructure/admin-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.