> 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/how-the-analysis-works/score.md).

# How the score works

The score is a weighted vote. A set of independent signals each cast a vote for or against, the votes get weighted by the token's [profile](/how-the-analysis-works/profiles.md), and the result is normalised to 0–100.

That's the whole idea.

## What votes

Each signal is computed independently, on its own evidence, and then normalised onto a common scale so they can be combined. They fall into five families:

| Family        | Asks                                                                                |
| ------------- | ----------------------------------------------------------------------------------- |
| **Momentum**  | Is the token stretched — has it run too far, or been sold too hard?                 |
| **Trend**     | Which way is it actually going, on the week and on the day?                         |
| **Structure** | Does the chart's shape mean anything — a base, a breakout setup, a topping pattern? |
| **Volume**    | Is participation growing or draining relative to its own recent history?            |
| **Flow**      | Are real transactions leaning to the buy side or the sell side?                     |

Which of these carries the most weight depends on the token's age profile — see [Token profiles](/how-the-analysis-works/profiles.md). The specific indicators, their thresholds and the weight table are the part that makes this analysis different from a stack of defaults, and they aren't published.

**A signal that doesn't have enough history is left out entirely** — not defaulted to zero. Dropping it is honest; including a neutral vote it never earned isn't.

## Reading the result

| Score  | Verdict                           |
| ------ | --------------------------------- |
| 70–100 | 🟢 Strong buy signal              |
| 55–69  | 🟡 Bullish, accumulation zone     |
| 45–54  | ⚪ Neutral, wait and see           |
| 30–44  | 🟠 Bearish, wait for better entry |
| 0–29   | 🔴 High risk, avoid for now       |

## Two things worth internalising

**A token with no signals at all scores around 50, not 0.** The normalisation maps "everything neutral" to the midpoint. A 50 means *no opinion*, not *bad* — and a token with too little history for most signals lands near the middle by construction.

**Thin data can't produce an extreme score.** The scale a token is measured against is fixed by its profile, not by how many signals happened to fire. So a token where only a handful could be computed gets pulled toward the middle and can't reach 100. That's intentional: thin evidence should produce a hedged verdict, not a confident one.

## What the score is not

It's a *composite*, not a prediction, and it's deliberately hard to move with any single indicator. Any one indicator you follow will disagree with it regularly — that's the point of a composite.

{% hint style="warning" %}
The score is a **technical** verdict. It does not know about the token's liquidity, its unlock schedule, or the fact that 40% of supply sits in six wallets funded by the same address. That's what [on-chain sentiment](/how-the-analysis-works/onchain.md) and [holder analysis](/the-telegram-bot/holder-analysis.md) are for — and it's why an 80 on a token with critical liquidity is not an 80.
{% 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/how-the-analysis-works/score.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.