> For the complete documentation index, see [llms.txt](https://docs.digitaldon.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitaldon.net/in-the-browser/web-analyzer.md).

# The Web Analyzer

The browser version. Same analysis, no Telegram required.

👉 [analyzer.digitaldon.net](https://analyzer.digitaldon.net)

(The project's home page is [digitaldon.net](https://digitaldon.net) — the analyzer lives on its own subdomain.)

Nothing to install, no account, no wallet connect. Open the page and paste a token.

## Using it

Paste a ticker, name or contract address and hit **analyze**. A progress row shows what it's doing — resolving, fetching the chart, analysing — and then the result panels render.

Multi-chain matches get a picker, same as the bot.

**Deep links** run an analysis on page load:

```
https://analyzer.digitaldon.net/?q=BONK
https://analyzer.digitaldon.net/?q=EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
```

Handy for pasting a pre-loaded analysis into a chat.

There's also a day/night toggle, because staring at a dark chart at 2pm is its own kind of pain.

## What's in the result

The same content as the [Telegram card](/the-telegram-bot/analysis-card.md) — score gauge, both trade plans, the four category reads, token stats, on-chain risk notes — laid out as panels instead of a single message, with an interactive chart.

Plus two panels the browser does better than Telegram can.

### x intelligence

Runs the [social sentiment](/the-telegram-bot/social-sentiment.md) analysis on the project's X account. Click to run — it isn't automatic.

### holder intelligence — the bubble map

The [holder and cluster analysis](/the-telegram-bot/holder-analysis.md), rendered as an interactive map. Each holder is a bubble sized by its share of supply; wallets that are demonstrably connected are drawn as a cluster.

You get:

* zoom in / out, fullscreen, reset view
* hover for wallet detail — address, percentage, role tags
* a legend for the role colours (sniper / bundle / insider / fresh / dev)
* **export png** and **export csv**

The CSV export is the fastest way to take the holder set somewhere else for your own digging.

## Same numbers as Telegram

The score you get in the browser is the score you get in Telegram — not "close to", the same integer. The two surfaces are checked against each other automatically before any change to the analysis can ship, and a mismatch blocks the release.

That matters more than it sounds. This is a tool whose entire output is a verdict; two different verdicts for the same token would be worse than no verdict at all.

## If a panel is missing

The two optional panels are the only part of the page that needs anything beyond your browser, and they can be switched off centrally. When they're off, the panel simply isn't rendered.

It **fails closed** on purpose: if the page can't confirm a feature is live, it doesn't draw it. Better a missing panel than a button that produces an error.

## What it can't do

The Web Analyzer is analyzer-only, on purpose. Group features — auto-scan, PNL cards, the leaderboard — are inherently Telegram things, and they stay there. The page links to the bot for those.


---

# 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://docs.digitaldon.net/in-the-browser/web-analyzer.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.