> For the complete documentation index, see [llms.txt](https://onza.gitbook.io/onza/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onza.gitbook.io/onza/onza-nexus/how-it-works.md).
# How It Works
ONZA NEXUS follows a structured process from **license selection and verification through weekly credits, withdrawals, and license completion**.
#### **1️⃣ Select a License**
Choose the ONZA NEXUS license that best matches your preferred access level.
Both **Standard** and **Institutional** license options are available.
#### **2️⃣ Complete Activation**
Pay the applicable **one-time License Activation Fee** for the selected license.
Each license has its own activation value and corresponding **maximum contractual gross credit ceiling**.
Each license is **personal, non-transferable, and limited to one operating cycle**.
#### **3️⃣ Complete Verification**
Complete the required **identity and compliance verification**.
Institutional licenses are subject to **enhanced verification requirements** before activation.
#### **4️⃣ License Becomes Active**
Once the required verification and activation process is successfully completed, the license becomes **Active**.
The active license term is up to **12 months (365 calendar days)**.
#### **5️⃣ Weekly Credits**
During the active license term, the system performs a **scheduled weekly cut-off** to determine whether the license is eligible for a credit.
Credits:
* Are based on **actual system performance**
* Are **variable**
* May be **zero**
* Are subject to the license's **maximum contractual gross credit ceiling**
There is **no fixed weekly amount or guaranteed credit percentage**.
#### **6️⃣ Withdraw Available Credits**
Credited and approved balances can be requested for withdrawal during the applicable **weekly withdrawal window**.
Withdrawal requests are subject to the applicable **security and compliance review**, as well as minimum amounts, fees, processing conditions, and limits.
Available settlement assets may include **USDC, USDT, and Bitcoin**, subject to jurisdiction, network/provider availability, and compliance approval.
#### **7️⃣ License Cycle Completion**
The active license cycle ends when either:
* The **12-month (365 calendar day) term is completed**, or
* The **maximum contractual gross credit ceiling is reached**
**whichever occurs first.**
Once the active cycle has ended, any outstanding eligible balance can be settled through the applicable withdrawal process.
{% hint style="info" %}
**Important:** Weekly credits are not guaranteed. They depend on actual system performance and may be zero. The maximum contractual gross credit ceiling is a **limit only**, not a promised or expected outcome.
{% endhint %}
---
# 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://onza.gitbook.io/onza/onza-nexus/how-it-works.md?ask=&goal=
```
`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.
