# README

> The Autonomous Execution Layer for On-chain Fixed Income

Haven AI is the first AI-powered protocol that automates capital allocation across stablecoins, RWAs, and quantitative strategies — creating a unified gateway between DeFi and TradFi fixed-income markets.

Powered by AI agent frameworks like **OpenClaw**, Haven enables 24/7 autonomous yield optimization with built-in risk intelligence.

***

### Quick Links

* 🌐 Website: [haven.financial](https://www.haven.financial)
* 🐦 Twitter/X: [@HavenAI\_](https://x.com/HavenAI_)
* 💬 Telegram: [t.me/AI\_Haven](https://t.me/AI_Haven)
* 📝 Medium: [medium.com/@HavenAI](https://medium.com/@HavenAI)
* 📖 Official Docs: <https://haven-11.gitbook.io/haven-ai-docs/>

***

### Core Products at a Glance

| Product                   | Description                                                                      |
| ------------------------- | -------------------------------------------------------------------------------- |
| **HavenClaw**             | AI execution engine — natural language → cross-chain strategy deployment         |
| **HavenScore**            | AI risk monitoring using market signals, sentiment, and whale activity           |
| **HavenSkill**            | One-click OpenClaw integration for querying best stablecoin yield paths          |
| **Unified Yield Gateway** | Access T-Bills, liquidity pools, and delta-neutral strategies from one interface |

→ Get started with the [Overview](/haven-ai-docs/getting-started/overview.md)


---

# 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://haven-11.gitbook.io/haven-ai-docs/readme.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.
