> For the complete documentation index, see [llms.txt](https://thesium.gitbook.io/thesium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thesium.gitbook.io/thesium-docs/the-solution.md).

# The Solution

The product is a Chrome extension. After installation and account sign-in, the trader continues to use their normal terminal. When they open a token page on AXIOM, GMGN, Photon, Padre or Basedbot, Thesium:

1. Reads the page URL and identifies which terminal and chain the page belongs to.
2. Extracts the token address either from the URL or, when the URL identifies a liquidity pool rather than a token mint, from the page DOM.
3. Sends parallel requests to the Thesium backend for token info, lore, AI summary, holders, KOL positions, feed, and a security audit.
4. Renders the result either in Chrome's native side panel, in a fallback popup window, and (optionally) in a compact in-page card triggered by a pill pinned to the bottom-right of the terminal page.

Instead of opening another tab or copying a contract address, the research loads beside the chart, right where the decision is being made.

The side panel exposes five views of the token:

* **AI · Lore.** A short read on what the token is, plus a sentiment direction (bullish / mixed / bearish), a conviction score out of 100, and the highlighted signals behind that score.
* **Audit.** For EVM tokens, a third-party honeypot / contract-risk simulation: buy/sell/transfer outcomes, tax rates, holder distribution flags, and a top-line verdict (safe / honeypot / unknown).
* **Feed.** A timeline of relevant social posts and thesis articles, with position-aware annotations where the author holds the token.
* **Holders.** Every tracked wallet on the address - tier-tagged, sized in USD, with current PnL.
* **KOLs.** A focused list of KOL-identified wallets with positions in the current pool, separated from the broader holders view so the highest-signal entries are always one tab away.

These five views are independent - each loads on its own deadline and degrades on its own. The panel renders progressively as data arrives, so the trader starts seeing answers within milliseconds of opening the token page.


---

# 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://thesium.gitbook.io/thesium-docs/the-solution.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.