> 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/invite-tracking/what-is-a-fake-invite.md).

# What is a fake invite ?

How does InviteLogger tells that an invite is valid or fake ?

{% hint style="info" %}
Please note that this definition of fake invite might change between bots
{% endhint %}

If you're an experimented or well advised InviteLogger user, you've probably seen that sometimes the bot consider invites as **fake**.

![Fakes invites in the /invites command](https://1233429419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_7KWGOtXaonSVC9Jd%2Fuploads%2Fxn9ANFZRG7YeKttDKgwJ%2Fimage.png?alt=media\&token=46a7de96-f00c-4aad-991e-dbaf8ca50e0e)

### What is a fake invite ?

An invite is counted as fake when it doesn't match server defined parameters. These parameters can be account age, profile pic, if already joined the server...

### How to configure the fake system ?

You can configure fake system parameters using the `/fakeConfig` command

![](https://1233429419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_7KWGOtXaonSVC9Jd%2Fuploads%2FFGqari9Gm88FdIh1b1UD%2Fimage.png?alt=media\&token=64de964b-8c58-4148-9132-7a6f3334d104)![](https://1233429419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_7KWGOtXaonSVC9Jd%2Fuploads%2FkepgPDObqBGzmgFfnNCK%2Fimage.png?alt=media\&token=9d9b8021-909a-4803-a8fa-c3140550c721)

{% content-ref url="/pages/qKZPBSeJzdYvjK8buW3g" %}
[Fake parameters](/general-topics/invite-tracking/what-is-a-fake-invite/fake-parameters.md)
{% endcontent-ref %}

{% hint style="warning" %}
Please note that settings change will only affect **future** joins. Currently fake invites will remain as they are.
{% endhint %}


---

# 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/invite-tracking/what-is-a-fake-invite.md?ask=<question>&goal=<user_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.