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

# Investment

For decades, the world’s top venture capital firms like a16z, Sequoia, and Fenbushi had access to opportunities that defined entire industries. They backed Coinbase, Binance, and Ethereum before the world knew their names, and they reaped the rewards that came with being early.

Until now, that level of access was off-limits to everyday investors. The rules of the game were written for insiders, with minimum checks in the hundreds of thousands and networks closed to all but the few.

WLTH flips that model. By tokenising and fractionalising private market opportunities, WLTH opens the door for anyone to participate in the companies shaping the future. From pre-IPO equity in tomorrow’s unicorns to curated Web3 funds and automated strategies, access is no longer a privilege, it’s a product.

This isn’t about chasing trends. It’s about building **smart, early exposure** to the next generation of success stories on terms that are transparent, liquid, and accessible to everyone.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wlth.xyz/investment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
