# Revenue Model

***

### **🔒 Vault Management Fees (Protocol Revenue)**

StAIke takes a percentage of the total yield generated from AI-allocated staking strategies.

| Fee Type              | Range    | Notes                                                               |
| --------------------- | -------- | ------------------------------------------------------------------- |
| Performance Fee       | 5–15%    | Applied only to profit, incentivizes user success                   |
| Management Fee        | 0.5–2%   | Charged based on total TVL in vaults                                |
| Exit/Reallocation Fee | 0.1–0.3% | Small fee when user unstakes early or switches strategies mid-cycle |

These fees are paid in-kind or settled in stAIke token or $KAT. TBD.

***

### 🤖 AI Strategy Access Tiers

Charge users based on access to premium AI staking strategies and performance boosts.

| Tier                     | Description                                                                  | Revenue Source                   |
| ------------------------ | ---------------------------------------------------------------------------- | -------------------------------- |
| Free Tier                | Access to basic vaults and yield routing                                     | Upsell funnel                    |
| stAIke Pro (Monthly Sub) | Access to optimized strategies, rebalance automation, performance dashboards | Paid in $KAT or USDC             |
| $KAT-Staker Exclusive    | Access only unlocked if user holds or stakes minimum $KAT                    | Drives $KAT demand, indirect rev |

***

### 🚀 Points & Boosts Marketplace

Introduce a marketplace where users can spend or redeem stAIke Points or tokens for:

* Yield multipliers (e.g., 1.2x on Morpho vault)
* Priority access to new strategies
* “Gasless” rebalance credits
* Vault strategy backtesting tools\ <br>

***

### 🧑‍🤝‍🧑 Partner Protocol Integrations (B2B Revenue)

Charge protocols or DAOs to be featured or included in stAIke’s AI routing system.

| Example                                         | Revenue                               |
| ----------------------------------------------- | ------------------------------------- |
| A new protocol wants to be included in vaults   | Listing or integration fee            |
| Treasury DAO wants to deploy capital via stAIke | % of managed assets or setup fee      |
| Liquidity program on Katana                     | Joint incentives with revenue-sharing |

***

### 🔂 Tokenomics Revenue Loops

* Fee Capture: Part of the protocol revenue is used to:
* Buy back & burn stAIke tokens
* Redistribute to token stakers or ve-lockers
* Points → Token Conversion: Points can be converted to token or $KAT, creating anticipation and buying pressure<br>

Staking Requirement: Some vaults or perks require locking stAIke tokens to participate<br>

***

### 💸 Usage of Revenue

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXf5PQqQxzWGFTismmNT9YeKvjwMDTeoN-n-U3rCVOgVtQLb4ECFK7rm0vvHgPAoqgW6rQlGDbEMFgIhf7dapdfKiaLagn50pYjPK8nGQ3LKKwiYUorNvssQy9iKEQyCP8CIfkjqKg?key=J5NW4dDSCw4EjdjIjZrCIA)

***

### 🪜 Tiered Access Model

| Tier     | Holding Requirements         | Perks                                          |
| -------- | ---------------------------- | ---------------------------------------------- |
| Free     | None                         | 3 free prompts/day, basic vaults               |
| Silver   | Hold ≥ 500 $STAIKE           | 10 prompts/day, yield simulator                |
| Gold     | Stake ≥ 2,000 $STAIKE        | Unlimited prompts, AI rebalancer, fee discount |
| DAO Tier | Pay via API key or bulk deal | Unlimited usage across treasury accounts       |


---

# 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://staike.gitbook.io/staike-whitepaper/revenue-model.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.