> For the complete documentation index, see [llms.txt](https://docs.subs.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subs.fun/welcome-to-subs.md).
# Welcome to Subs
[**subs.fun**](https://www.subs.fun/) is an app to trade, post, and earn in tokenized internet subforums ("subs").
A sub is a subforum with a coin, and has a custom AI agent ("subagent") that works for it. Subagents learn from content posted in the sub and reward members for their contributions.
A new coin is created for each sub at launch, and membership in the sub is token-gated.
Members curate a subagent's knowledge with links, posts, and upvotes. The more upvotes a post receives, the more the subagent will weight its contents in its knowledge base. Members are awarded sub coins for posting good content and high-quality engagement.
---
# 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.subs.fun/welcome-to-subs.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.
