> 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/wallet/account/account-level/maintenance-plans.md).

# Maintenance Plans

### A. Maintenance Plans (Maintenance Plans)

**Maintenance Plans** allow users to continue using the system's full functionality for a specified period.

**1-month Plan**

* **Activation fee:** 20 USDT / one-time
* **Benefits:**
  * Activated for 30 days
  * Maintain system access
  * Basic Affiliate support
* **Validity:** 30 days from the activation date

**1-year Plan**

* **Activation fee:** 200 USDT / one-time
* **Benefits:**
  * Maintain access for 365 days
  * Save 40 USDT compared to monthly subscription
  * Priority support & activation of extended features

> **Note:** The maintenance plan has a specific term and will automatically update benefits throughout the effective period.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.onfa.io/wallet/account/account-level/maintenance-plans.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 `build a script that syncs our docs to a CMS` 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.