> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/help-center/pt-br/cobranca-e-pagamentos/how-does-your-billing-cycle-work.md).

# Como funciona o seu ciclo de cobrança?

Entenda como funciona o ciclo de cobrança da Oxylabs, incluindo o momento do pagamento e as regras de renovação.

Nosso ciclo de cobrança para planos de autoatendimento começa no dia da compra. Os pagamentos do próximo ciclo de cobrança são autorizados automaticamente.

Com outros planos, salvo indicação em contrário, o ciclo de cobrança começa no primeiro dia do mês. Uma fatura será enviada a você e deverá ser paga em até sete dias.

Embora você não possa alterar a data de renovação do seu ciclo de cobrança, você sempre pode adicionar saldo ou fazer upgrade do seu plano a ნებისმки momento.


---

# 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://developers.oxylabs.io/help-center/pt-br/cobranca-e-pagamentos/how-does-your-billing-cycle-work.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.