# NFT Dive Engine

The **NFT Dive Engine** is the Umiverse's unique concept of creating a fun, customizable way to increase the conversion of Dive Points into $UMI. The current model is a concept only and may be subject to change at the Umiverse’s full launch at a later date.&#x20;

The Dive Engine system will be placed under the **“Wallet Section”** of the platform

The Dive Engine is split into three different components. The Dive Engine is only ‘operational’ when all three components are present. These components are **Turbine, DriveTrain and Capacitor**. Each component can be interchangeable.&#x20;

| Part Type   | Part Model | Description                                                          | Cost       |
| ----------- | ---------- | -------------------------------------------------------------------- | ---------- |
| Turbine     | TB-0001    | Basic Turbine model Add 0 bonus to your Dive Point $UMI Conversions. | $10 USDC/T |
| Turbine     | TB-0001S   | Basic Turbine model with 2% bonus on your total $UMI Conversions     | $50 USDC/T |
| Drive Train | DT-FHK-00  | Fahad Kingdom Drive Train, convert Fahad Kingdom Dive Points to $UMI | $25 USDC/T |
| Drive Train | DT-SS-00   | “Game 1” Drive Train, convert Dive Points to $UMI                    | $25 USDC/T |
| Capacitor   | CX-0001    | Basic small sized Capacitor Hold a maximum of 100 Dive Points        | $50        |
| Capacitor   | CX-0001M   | Basic medium sized Capacitor, hold a Maximum of 150 Dive Points      | $80        |

\
Dive Engine components can be purchased from the Umiverse Marketplace and the above is only illustrated as an example.&#x20;


---

# Agent Instructions: 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:

```
GET https://gitbook.umiverse.io/umiverse-gitbook/tokenomics/nft-dive-engine.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
