> For the complete documentation index, see [llms.txt](https://docs.trnch.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trnch.fun/tia.md). # TIA TIA (Trnch Intelligence Agency). Every new Robinhood Chain token is checked before it can reach the Heat. TIA (Trnch Intelligence Agency) has run 24/7 on Robinhood Chain since 13 October 2026 and has caught up on the chain's entire history since its launch. It checks every new token before it can appear in the Heat. ## What TIA has seen The figures live on the [TIA track record](https://trnch.fun/tia) ([live figures](https://trnch.fun/tia)): every token Trnch spotted, what TIA decided and when, which ones rugged, and every rug on Robinhood Chain. Each UTC day is frozen with a SHA-256 hash and a Merkle root. ## How it works, in short TIA cross-checks each new token against everything it has in memory: past rugs, the contracts, deployers and pools behind them, and live trading on the chain. A token that matches a known scam pattern is flagged as soon as it is created, before it can be listed. Every new type of rug feeds that memory and makes TIA more reliable. TIA adapts on its own, so the next scam that reuses the same tricks is caught earlier. ## What you see on Trnch * A token TIA clears can enter the [Heat](/heat.md). * A token judged high risk is kept out of the Heat and listed under **Flagged**, with a public risk category. On the website it shows a High risk warning and a Buy anyway button; through the Bot API and the MCP server, Trnch refuses to build the swap. * If a rug still happens despite every filter, the token leaves the Heat at once and its pattern goes into memory. ## What we do not publish We tune TIA continuously and do not publish its rules, so scammers cannot adapt to them. No filter removes every risk. Read the [Risk Disclosure](/legal/risk.md) before you trade new tokens. --- # 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.trnch.fun/tia.md?ask=&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.