> For the complete documentation index, see [llms.txt](https://docs.marinade.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marinade.finance/official-links.md).
# Official Links
If you want to join us, here is where you can find us!
These are the only official Marinade channels. If a link, wallet prompt or support request reaches you from anywhere else, it is not from Marinade.
{% hint style="danger" %}
**Marinade will never DM you first, never ask for your seed phrase or private key, and never ask you to "validate", "sync" or "migrate" your wallet.** Support does not happen in direct messages. Always reach the app through `app.marinade.finance` and check the domain before connecting a wallet. Anyone who contacts you claiming to be Marinade support is a scammer.
{% endhint %}
***
## Use Marinade
Staking app:
Main website:
***
## Interact With Us
Discord:
X:
YouTube:
Forum: [https://forum.marinade.finance/](https://forum.marinade.finance)
***
## Follow Our Work
Blog:
Documentation:
Help center:
GitHub organisation:
Audits:
Press kit:
***
## Data And Dashboards
Marinade Stats: [https://stats.marinade.finance/](https://stats.marinade.finance)
Validator explorer:
Protected Staking Rewards validator dashboard:
Governance and DAO treasury on Realms:
---
# 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.marinade.finance/official-links.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.