> For the complete documentation index, see [llms.txt](https://docs.invitelogger.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.invitelogger.me/general-topics/integrations/doublecounter.md).
# Double Counter
Link InviteLogger & Double Counter
## Overview
This integration allow you to make sure your inviters don't invite alt or automated bots by using [**Double Counter**](https://dashboard.dcounter.space/) captcha system to consider an if an invite is either valid or fake.
## Tutorial
Before doing anything, enable the Double Counter integration in both [**InviteLogger**](https://invitelogger.me/dashboard) and [**Double Counter**](https://dashboard.dcounter.space/) dashboard and make sure both bots are invited to your server.
It should look like this once enabled
Once you've something like this, it is now time to setup the fake system to work with Double Counter\
To do so we'll use the **/fakeConfig** command and add the double counter verification requirement as a mandatory requirement for an invite to be counted as valid.
\
*➡️ It means that all new member invites that aren't verified through* [***Double Counter***](https://dashboard.dcounter.space/) *verification will be counted as fake for the inviter.*
---
# 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.invitelogger.me/general-topics/integrations/doublecounter.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.
