> For the complete documentation index, see [llms.txt](https://kaiainvestmentpartners.gitbook.io/kaiainvestmentpartners-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kaiainvestmentpartners.gitbook.io/kaiainvestmentpartners-docs/overview/what-we-do.md).

# What We Do

KIP operates dual strategies.

**On-chain yield products (Y-Series)**

KIP designs and operates the Y-Series, yield products that hold real-world assets and issue as tokens on Kaia. Each product raises capital for a defined asset strategy, tokenizes the strategy's yield, and distributes the tokens through an on-chain vault. Investors hold the tokens on-chain. The Y-Series currently comprises two products, Yield8 and Yield5, covering different points on the risk-return spectrum.

**Venture fund**

KIP runs a venture fund that invests in companies driving stablecoin adoption, across payments, infrastructure, and applications. It is primarily early- to growth-stage and weighted toward Asia. Its terms are set out in separate venture materials.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://kaiainvestmentpartners.gitbook.io/kaiainvestmentpartners-docs/overview/what-we-do.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.