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

# Assinatura e planos

* A assinatura fica em **Configurações → Assinatura**: plano, próxima cobrança, troca de cartão, upgrade, downgrade agendado e cancelamento.
* O teste grátis dura 3 dias. O upgrade é pago na hora e liberado depois da confirmação do pagamento; no teste, o upgrade encerra o teste.
* No **Basic** ficam indisponíveis, com aviso de upgrade: sugestão de resposta por IA no chat, replay automático, automação de e-mail de convite e webhooks/integrações avançadas. O "Gerar com IA" do editor funciona em todos os planos. Limites: 100 participantes simultâneos, 5 webinars ativos e 3 usuários.
* **Pro:** 1.000 participantes, 15 webinars ativos e 8 usuários. **Elite:** ilimitado.
* Os limites em uso aparecem na Visão Geral.

Compare os planos em [Planos e perguntas frequentes](/webinartools/documentation/planos-e-perguntas-frequentes/plans.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://webinartools.gitbook.io/webinartools/documentation/referencia/subscription.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.