> For the complete documentation index, see [llms.txt](https://docs.starke.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.starke.finance/readme.md).

# Welcome

## Welcome to Starke Finance

At Starke Finance is a investment platform natively built over Solana. We are pioneering the next generation of capital markets by bridging traditional finance products such as managed funds empowered by blockchain technology.&#x20;

In this GitBook, you’ll find an overview of our products, our team, compliance frameworks and long-term vision. Whether you’re an investor, a fund manager, or staker, this guide will help you understand how we operate, why we exist, and where we are heading.

Welcome to the future of investing — welcome to **Starke Finance**.

### Join Our Community <a href="#join-our-community" id="join-our-community"></a>

We'd love to hear from you. Please consider joining us any of our [social networks](https://starke.finance/contact). You can also contact us at <contact@starke.finance>


---

# 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://docs.starke.finance/readme.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.
