> For the complete documentation index, see [llms.txt](https://wiki.onfa.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.onfa.io/sp/cartera/cuenta/nivel-de-cuenta/planes-de-mantenimiento.md).

# Planes de Mantenimiento

#### A. Planes de mantenimiento (Planes de mantenimiento)

**Planes de mantenimiento** permiten a los usuarios continuar utilizando la funcionalidad completa del sistema durante un período especificado.

**Plan de 1 mes**

* **Cuota de activación:** 20 USDT / pago único
* **Beneficios:**
  * Activado por 30 días
  * Mantener acceso al sistema
  * Soporte básico para afiliados
* **Validez:** 30 días desde la fecha de activación

**Plan de 1 año**

* **Cuota de activación:** 200 USDT / pago único
* **Beneficios:**
  * Mantener acceso durante 365 días
  * Ahorra 40 USDT en comparación con la suscripción mensual
  * Soporte prioritario y activación de funciones extendidas

> **Nota:** El plan de mantenimiento tiene un plazo específico y actualizará automáticamente los beneficios durante todo el período vigente.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.onfa.io/sp/cartera/cuenta/nivel-de-cuenta/planes-de-mantenimiento.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.