> 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/transparency/alternatives.md). # Alternatives How Thesium relates to the surfaces a trader might already be using. ## vs manual workflow The status quo for serious research is the multi-tab manual workflow described in The Problem. Thesium replaces it. Thesium's panels equal or exceed the data quality of the manual workflow on the four mature chains, and they arrive on the same screen in seconds rather than minutes. The honest gap: a trader who has built bespoke spreadsheets, alerts, and dashboards over years may have data points Thesium does not surface. Thesium is the 90th-percentile workflow for the 95th percentile of tokens. Edge cases at the bleeding edge still benefit from bespoke setup. ## vs single-purpose dashboards Holder dashboards, KOL trackers, and honeypot scanners each solve one of Thesium's panels. They typically have deeper drill-down within their slice - full transaction history per wallet, custom filters, historical exports. Thesium does not match this depth in any single slice. The tradeoff: depth in one slice vs combined view across five. For research at the moment of decision, the combined view wins. For deep-dive analytics after the fact, the single-purpose tools are still useful. ## vs terminal-native research panels Some terminals embed light research panels of their own. These are usually shallower than Thesium and locked to one terminal. A trader who uses only one terminal might find the native panels sufficient. A trader who uses multiple terminals gets two benefits from Thesium: depth that the native panels lack, and consistency across terminals so the workflow is the same regardless of where the token lives. ## vs Telegram-based research bots Telegram-bot ecosystems exist for token analysis. They are useful in the channels they live in. They are not useful at the moment the trader is on the chart, because the chart is on the screen and Telegram is on the phone. Thesium and Telegram research are not substitutes. They cover different moments in the workflow. --- # 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://thesium.gitbook.io/thesium-docs/transparency/alternatives.md?ask=&goal= ``` `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.