# AI Calculator

### :brain: AI Strategy Engine

* Powered by large language models (LLM) fine-tuned on DeFi and Economic data.
* Converts user wallet signals, DeFi yields and risk metrics into strategy prompts
* Generates personalized staking strategies and yield portfolio allocations.
* Explains recommendations in natural language for transaprency

> Example prompt:\
> “This wallet prefers ETH-native strategies and avoids stablecoin pools. Recommend low-volatility yield options on Ethereum and Arbitrum.”

***

### :abacus: Risk Weighted Model

* Every yield opportunity is scored on multiple risk vectors:
  * Smart contract audit status
  * Protocol age and TVL trends
  * Token volatility and liquidity
  * Impermanent loss risk
  * Governance and rug pull flags
* Outputs a **risk-adjusted yield score** per opportunity.

> 🔍 Users can customize their own risk profiles: conservative, balanced, or aggressive.

***

### :loop: Real-Time Optimization Loop

* The protocol continuously:
  * Monitors market changes
  * Tracks protocol risks
  * Updates the user’s recommended positions
* Users receive optional AI notifications for rebalancing or exit signals.

***

### :zap: Execution Engine (1-Click Deploy)

* Users can act on AI recommendations via a seamless UI.
* Supports:
  * Native execution (via wallet)
  * Cross-chain bridging/staking (with integrated routers)
  * Gas fee estimation and batching
* Advanced users can customize allocations before confirming.


---

# 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/protocol/ai-calculator.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.