> For the complete documentation index, see [llms.txt](https://docs.flap.sh/flap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flap.sh/flap/developers.md).

# Developers

This guide is structured to introduce you to the different facets of developing with Flap. It's recommended to first familiarize yourself with the **basic mechanisms of Flap**. Once you're comfortable with the fundamentals, proceed to the section that suits your specific role:

* **Wallets & Terminal & Bot Developers:** For developers who want to build an indexer for Flap and trade tokens launched from Flap
* **Launcher Developers:** For applications leveraging Flap's infrastructure to launch tokens.
* **Vault Developers:** For those interested in building upon Flap's Vault system.

Please read the section corresponding to your role for detailed instructions and guidance.

* [Basic & Mechanism](/flap/developers/basic-and-mechanism.md)
* [Wallets & Terminal & Bot Developers](/flap/developers/wallet-and-terminal-and-bot-developers.md)
* [Launcher Developers](/flap/developers/token-launcher-developers.md)
* [Vault Developers](/flap/developers/vault-developers.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.flap.sh/flap/developers.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.