> For the complete documentation index, see [llms.txt](https://wiki.privai.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.privai.cloud/ecosystem-components/token-intel.md).

# Token Intel

Token Intel modules help users review token and project risk before they buy, promote, join, or interact with a project.

## What It Helps Answer

* Does this token show obvious risk signals?
* Does the deployer have suspicious history?
* Is liquidity thin, recently changed, or concentrated?
* Are project details reused across other launches?
* Do third-party risk providers agree or conflict?

## Active Modules

| Module                        | Purpose                                                                                     | Status     |
| ----------------------------- | ------------------------------------------------------------------------------------------- | ---------- |
| **token\_risk.report**        | Combines token profile, market, contract, metadata, and reputation checks.                  | MVP active |
| **rugcheck.lookup**           | Pulls Solana token risk signals from RugCheck's public API.                                 | MVP active |
| **mint\_account.inspect**     | Reads Solana mint/account metadata, owner/program details, and recent transaction samples.  | MVP active |
| **liquidity\_watch.view**     | Uses DEX Screener liquidity and market context to summarize pair health.                    | MVP active |
| **deployer\_history.map**     | Reviews Solana mint history, launch participants, and pair context.                         | MVP active |
| **recycled\_project.inspect** | Looks for reuse signals across token profiles, domains, contracts, and public project data. | MVP active |

## Report Focus

Token Intel reports should make risk easier to evaluate without pretending to guarantee safety.

Useful report outputs include:

* Contract and mint context.
* Liquidity and pair health.
* Risk provider signals.
* Reused domains, socials, names, or metadata.
* Deployer and launch pattern context.
* Suggested next checks before interacting.

## Data Sources

| Source                  | Used For                                                            |
| ----------------------- | ------------------------------------------------------------------- |
| **Solana RPC / Helius** | Mint metadata, token accounts, transaction samples, wallet context. |
| **DEX Screener**        | Pair data, liquidity, market context, socials, and profile links.   |
| **RugCheck**            | Solana token risk signals.                                          |
| **Etherscan / GoPlus**  | Ethereum enrichment where configured.                               |


---

# 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://wiki.privai.cloud/ecosystem-components/token-intel.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.