> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/pt-br/faq/c142/c144/q395.md).

# Como começo a usar a versão offline?

Report and Run: Offline está disponível no [Google Play Store](https://play.google.com/store/apps/details?id=com.jtt.reportandrun) e o [App Store](https://itunes.apple.com/us/app/report-and-run/id1168519465?mt=8)Oferecemos um plano gratuito para sempre e um plano pago com recursos adicionais. Novos usuários podem testar os recursos pagos por 30 dias antes de iniciar uma assinatura anual. Após o período de teste de 30 dias, os usuários serão cobrados em US$ 10 por ano (na sua moeda local).&#x20;

Se você quiser ver como criar seu primeiro relatório em menos de um minuto, veja o nosso [vídeo de início rápido](https://youtube.com/shorts/QWzmUDSGMuQ?feature=share).

Também temos um [guia de início rápido](https://docs.reportandrun.com/manual/pt-br/report-and-run/quick-start-guide.md) que mostra como criar um relatório.

## Relacionado

* [FAQ: Quais são os recursos adicionais incluídos no plano pago do Report and Run: Offline?](https://docs.reportandrun.com/manual/pt-br/faq/c142/c147/q413.md)
* [FAQ: Como começo um período de teste para experimentar o app?](https://docs.reportandrun.com/manual/pt-br/faq/c142/c149/q430.md)
* [FAQ: Como faço para assinar o plano pago do Report and Run: Offline?](https://docs.reportandrun.com/manual/pt-br/faq/c142/c144/q397.md)
* [FAQ: Quais métodos de pagamento posso usar para assinar o app?](https://docs.reportandrun.com/manual/pt-br/faq/c142/c148/q424.md)
* [FAQ: Quais são as diferenças entre Report and Run: Integrate e Report and Run: Offline?](https://docs.reportandrun.com/manual/pt-br/faq/c142/c143/q388.md)


---

# 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.reportandrun.com/manual/pt-br/faq/c142/c144/q395.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.
