> 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/readme.md).

# Welcome to DigitalDon

DigitalDon takes a token — a ticker, a name, or a contract address — and gives you back a straight answer: a chart, a score out of 100, where you'd buy, where you'd take profit, and what's wrong with it.

No dashboards to configure. No 14 indicators to interpret yourself. One input, one card.

There are two ways to use it:

|                     | What it is                                  | Where                                                      |
| ------------------- | ------------------------------------------- | ---------------------------------------------------------- |
| 🤖 **Telegram bot** | `/don <token>` in a DM or in your group     | [@DigitalDonAnalyzeBot](https://t.me/DigitalDonAnalyzeBot) |
| 🌐 **Web Analyzer** | Same thing in a browser, nothing to install | [analyzer.digitaldon.net](https://analyzer.digitaldon.net) |

The project's home page — what DigitalDon is, in one screen — is [digitaldon.net](https://digitaldon.net).

Both surfaces run the **exact same analysis**. Not "similar" — identical, down to the integer, and that's checked automatically before any change ships.

## What you actually get

* **A candlestick chart** with the support and resistance the analysis used — so you can see where the numbers came from instead of trusting them blind.
* **A score, 0–100**, weighted differently depending on how old the token is. A three-day-old memecoin and a two-year-old blue chip do not deserve the same treatment.
* **Two trade plans** — a short-term one (days) and a long-term one (weeks), each with an entry zone and a take-profit zone.
* **On-chain reality check** — liquidity vs market cap, FDV overhang, buy/sell pressure. The stuff that decides whether the chart even matters.
* **Holder analysis** (optional) — who holds this, are their wallets connected, did the same funder pay for twelve of them ten minutes before launch.
* **Social sentiment** (optional) — is the project's X account real, or three weeks old with bought followers.

And in a group, on top of all that:

* **Auto-scan** — someone pastes a contract, the bot answers with a compact card.
* **PNL cards** — receipts for who called what, and what it did after.
* **Leaderboard** — the group's callers ranked by how their calls actually performed.

## Where to go next

* **Never used it?** → [Quickstart](/getting-started/quickstart.md)
* **Setting it up properly?** → [Setting it up](/the-telegram-bot/setup.md)
* **Want every command?** → [Command reference](/the-telegram-bot/commands.md)
* **Got a card and want to read it properly?** → [Reading the analysis card](/the-telegram-bot/analysis-card.md)
* **Want to know what the score means?** → [How the score works](/how-the-analysis-works/score.md)

{% hint style="warning" %}
None of this is financial advice. It's a tool that reads charts and chain data faster than you can. It has no idea what's about to be announced on Twitter. Always DYOR.
{% endhint %}


---

# 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/readme.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.