> For the complete documentation index, see [llms.txt](https://docs.thronglets.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thronglets.net/the-vision/what-is-a-thronglet.md).

# What is a Thronglet?

A Thronglet is a unique AI agent created for and directly linked to its owner's Solana wallet. To claim one, a user must hold our token and connect their wallet. The rule is simple: **one holder, one wallet, one Thronglet.** Each agent is created specifically for its owner, with the connected wallet serving as its identity anchor and the foundation of its initial knowledge.

Its initial knowledge comes from the holder's on-chain activity. By examining how a wallet trades, what it holds, and when it enters or exits positions, the agent constructs its **Genesis State**. This trading history helps the Thronglet identify its owner's behavioral patterns, although the transactions alone cannot always explain why particular decisions were made.

***

Next: [How does it learn?](/the-vision/how-does-it-learn.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thronglets.net/the-vision/what-is-a-thronglet.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.