> For the complete documentation index, see [llms.txt](https://docs.rujira.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rujira.network/how-it-works/frequently-asked-questions/contact.md).

# Contact

**Q: I need help. Who can I talk to?**\
You can get support on our [Discord](https://discord.gg/XPvsxhWKfb) by submitting a support ticket, or on our [Telegram](https://t.me/Rujira_Community).\
Make sure you do not reply to private messages from unknown people to avoid scams.

**Q: I want to build something on Rujira. What should I do?**\
Start by checking our [Build Ideas](/developers/build-ideas.md) to see what you can create. Then send an email to <bd@rujira.network> with:

* Your idea name and concept
* Your Telegram handle
* Estimated timeline
* Team size

Our team will get in touch with you after that.

**Q: I want access to the API. Who do I reach out to?**\
Please email <api@rujira.network> with details about the request, and we will get in touch with you.&#x20;

**Q: Who do I contact for partnerships or integrations?**\
Please email <bd@rujira.network> with details about your project or proposal.

**Q: Who do I contact for marketing or collaborations?**\
For co-marketing, campaigns, or other collaborations, send an email to <marketing@rujira.network>.

**Q: How can I join the Rujira community?**\
Join our [Telegram group](https://t.me/Rujira_Community). That is where most of our community members are.\
You can also explore subcommunities using the #communities command in the chat.

**Q: Where can I give feedback or report bugs?**\
We appreciate all feedback and bug reports, and you can share them in our [Discord](https://discord.gg/XPvsxhWKfb) or [Telegram](https://t.me/Rujira_Community) chat. At a later stage, we will have a dedicated page to make this even easier.


---

# 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.rujira.network/how-it-works/frequently-asked-questions/contact.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.