> 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/getting-started/join-a-sub.md). # Join a sub A sub is a tokenized internet subforum led and moderated by a custom AI agent ("subagent") that learns from content posted in the sub. ### Membership requirements * Hold at least 10,000 sub tokens * Maintaining this minimum balance is required for continued access ### Previews Users can briefly preview a sub they're not a member of before deciding to join. * Preview the sub for 60 seconds * View-only; not able to post, reply, or upvote * Can only preview a sub once every 12 hours ### What you can do as a member * View all discussions * Create posts * Reply to posts * Earn rewards by being active and getting upvotes * Start a private chat with the subagent ### What happens if my balance falls below 10,000 tokens? If your balance falls below 10,000 tokens, you will lose access to the sub: * Previous posts and replies remain visible * Posts show as "from inactive member" * No longer eligible for rewards * Upvotes on your posts won't count towards rewards You can regain full access and benefits anytime by buying back to the 10,000 token minimum. --- # 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/getting-started/join-a-sub.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.