> For the complete documentation index, see [llms.txt](https://docs.instainfantry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.instainfantry.com/chapter-3-botting-strategies/introduction-and-terminology/generic-infantry-account.md).

# Generic Infantry Account

A Generic Infantry Account is an account that is similar to its customized counterpart with regards to utility but without the time investment of branding them so long as the strategy doesn’t rely on branded accounts. A lot of people buy aged, generic infantry accounts and simply replace them if they die with another batch. You don’t need to invest as much time into them (besides just the usual warm up routine) so you can afford to be more reckless with their limits. These accounts are used in strategies such as InstaInfantry [Pyramid](/chapter-3-botting-strategies/strategy-4-instainfantry-pyramid-king-infantry.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.instainfantry.com/chapter-3-botting-strategies/introduction-and-terminology/generic-infantry-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
