> 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/fake-parameters.md).
# Fake parameters
With the /fakeconfig invites, you can configure what requirements joining members must fill for their join to be counted as valid invite.
You can know the reason of a fake invite through the /info command
#### Fake parameters list
Account age
Joining account must be older than a custom amount of days
Variable: Amount of days
Self inviting
Joining members must not join **using their own invite**
Profile picture
Joining members must have a custom profile picture
💰 First join
Joining members must join the server for the first time to be counted as valid
💰 Role requirement
Joining members must receive a specific role
Variable: Role to give
💰: An [InviteLogger Gold](/premium/gold.md) subscription is required
---
# 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/fake-parameters.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.