> For the complete documentation index, see [llms.txt](https://ovro.gitbook.io/ovro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ovro.gitbook.io/ovro-docs/resources/official-links.md).

# Official links

The only official OVRO channels. Anything else is not us.

|               |                                                                          |
| ------------- | ------------------------------------------------------------------------ |
| Website       | [ovro.fun](https://ovro.fun)                                             |
| Documentation | [ovro.gitbook.io/ovro-docs](https://ovro.gitbook.io/ovro-docs)           |
| X             | [@ovrofun](https://x.com/ovrofun)                                        |
| Contracts     | [Contracts](/ovro-docs/security/contracts.md) page of this documentation |

## Stay safe

* There is no OVRO app to download, no airdrop claim page and no support chat that asks for your wallet.
* Nobody from OVRO will ever message you first or ask for your seed phrase, private key or a "verification" signature.
* $OVRO will launch on **Pons V2** only. Its contract address will be published here and on the website. Tokens with the same name anywhere else are not OVRO.
* Before signing, check that the transaction goes to an address listed on the [Contracts](/ovro-docs/security/contracts.md) page.


---

# 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://ovro.gitbook.io/ovro-docs/resources/official-links.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.