> For the complete documentation index, see [llms.txt](https://fraudify.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fraudify.gitbook.io/docs/readme.md). # Fraudify Documentation Fraudify is an AI-powered, always-on Discord security system designed to protect online communities from impersonation attacks, malicious links, and wallet-draining scams. It combines deterministic identity checks, real-time moderation, a local security database, and a Retrieval-Augmented Generation threat engine to detect and respond to threats with minimal moderator involvement. ## What Fraudify Protects Against * Staff and administrator impersonation * Unverified and malicious links * Fake mint pages and phishing domains * Wallet drainer links * Repeated scam accounts across protected servers * Delayed manual threat investigation ## Core Capabilities * Real-time member and message monitoring * Automatic impersonator detection and banning * Unauthorized-link deletion * Staff and administrator exemptions * AI-assisted message auditing * Verified server directory responses * Community-powered scammer reporting Use the navigation menu to learn how Fraudify works, configure the bot, use its security features, and understand its technical architecture. --- # 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://fraudify.gitbook.io/docs/readme.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.