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

# Community 

#### Community and Support

1. **Support Channels**: Users can get support through our official Discord server, Telegram group, and support email.
2. **Community Engagement**: Join our community on social media platforms to stay updated with the latest news and participate in discussions.
3. **Feedback and Suggestions**: We value our community's feedback and encourage users to share their suggestions for improving the platform.

#### Miscellaneous

1. **Partnerships**: OpenALCHI collaborates with various projects to introduce unique elements and combinations, enhancing the overall ecosystem.
2. **Revenue Model**: OpenAlchi generates revenue through minting fees, marketplace transaction fees, and other in-game transactions.


---

# 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.openalchi.xyz/overview/community.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.