# Finding well performing callers

Docs coming soon.

## Use filtering dashboard

<details>

<summary>How is the Caller Score calculated? </summary>

The score's main objective is to summarize the most important metrics for a caller in a single number between 0 and 100, making it easier to find good callers.

Firstly, every call gets a specific score using the following metrics:

* ATH profit (if ATH is 1000% for just a minute, and the tokens die a  few minutes after the call, the score will be low, we are targeting for more long-term successful tokens)
* Current profit (higher the better)
* Volume change after the call compared to before the call
* Market cap (making a good call with a bigger market cap is harder)
* If there is very little time between a token creation (\~5 minutes) and the call, some points are removed (many callers are paid in advance for calling tokens at launch time, but group followers won't be able to make an entry like that)
* Remove points if a called token is a scam or the liquidity is very low.

Then we get all the calls for a caller in a selected interval and calculate the final caller score based on:

* Average call score described in the previous step
* Average ATH percentage
* Average Current percentage
* Last time the caller made a call
* How many scams were called
* Gem Bonus: how many 10X tokens were found
* Good calls consistency
* Number of first calls from all of the tracked callers

</details>


---

# Agent Instructions: 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://docs.blokiments.com/features/caller-tracker-and-analysis/finding-well-performing-callers.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.