> For the complete documentation index, see [llms.txt](https://docs.reloadsol.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reloadsol.app/understand-risk/rug-detection-and-knowledge-graph.md).

# Rug detection & knowledge graph

How reloadSol's inline risk chips and public Knowledge Graph help you spot bundled launches, thin liquidity, and risky deployers before buying.

**TL;DR:** reloadSol surfaces inline risk indicators on `/buy` and a visual **Knowledge Graph** at `/knowledge-graph` so you can check holder concentration, liquidity depth, and deployer history before signing a buy.

[Open Knowledge Graph →](https://reloadsol.app/knowledge-graph)

***

## What you can inspect before buying

| Signal                       | Where you see it                                                                         | What to watch for                                                            |
| ---------------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| **Inline risk chips**        | [Bulk Buy](https://reloadsol.app/buy/solana)                                             | Flags high top-holder concentration, thin liquidity, or metadata anomalies.  |
| **Deployer provenance**      | [Knowledge Graph](https://reloadsol.app/knowledge-graph)                                 | Shows whether a token creator has a history of failed or rugged launches.    |
| **Bundled / sybil clusters** | [Knowledge Graph](https://reloadsol.app/knowledge-graph)                                 | Visualizes wallets funded from the same source or buying together at launch. |
| **Price impact cap**         | [Bulk Buy](https://reloadsol.app/buy/solana) & [Sell](https://reloadsol.app/sell/solana) | Automatically discards routes exceeding **15%** price impact.                |

***

## Honest limits of automated detection

{% hint style="warning" %}
**Detection is advisory—not a guarantee.** Many risk signals on reloadSol run in observational (shadow) mode, and newly launched tokens may have incomplete holder or deployer history (shown honestly as unknown rather than "clean"). Always verify liquidity and never size a trade assuming a filter will save you from a rug pull.
{% endhint %}

***

## Related

* [Charts, watchlist & discovery](https://docs.reloadsol.app/trade/charts-watchlist-and-discovery.md)
* [Stay safe on reloadSol](https://docs.reloadsol.app/start-here/safety-and-security.md)
* [Risk disclosure](https://docs.reloadsol.app/help/risk-disclosure.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reloadsol.app/understand-risk/rug-detection-and-knowledge-graph.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
