> 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/product-overview/features.md). # Features ## Automated Impersonator Ban Fraudify automatically bans accounts whose usernames, display names, or nicknames exceed configured similarity thresholds against registered staff handles. Checks run when a member joins or updates their profile. ## Real-Time Link Moderation External links posted by standard users are checked immediately. Unverified links are deleted, and the sender receives a temporary warning banner. ## Staff and Administrator Exemption Discord administrators and identities registered in `server_admins` bypass link restrictions. ## RAG Message Auditing Users can right-click or long-press a suspicious message and select: **Apps → Analyze Message** Fraudify returns a concise, private security report containing: * Handle-similarity findings * Threat status * Recommended action ## Verified Directory Listener Fraudify responds to keywords such as `link`, `faq`, and `admin` with approved server links, project information, and staff handles. ## Global Red Alert Blacklist The `/flags` command allows protected communities to report suspected scammers and increase their community threat score. --- # 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/product-overview/features.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.