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

# Why Ventuals?

## We're creating markets for anyone to get exposure to innovation.

Our mission is to align the public's interest in transformative technology with real, tradable markets.

People see innovation happening all around them and want ways to get exposure. They don't want to get left behind — but today, it can be difficult to act on that interest.

We’re changing that. Ventuals makes breakthrough technologies tradable — across private markets, emerging sectors, and thematic clusters — letting anyone position for the world they believe is coming.

### We started with private companies

Our first markets were perps for pre-IPO company valuations, bringing price discovery, transparency, and tradability to a historically opaque and illiquid market.

On Ventuals, you can go long or short the valuation of blue chip private companies, without waiting for an IPO. No accreditation, paperwork, or million-dollar checks needed.

### And expanded to thematic indices of public stocks

Innovation and frontier technology starts at private companies, but it doesn't stop there.

You can now trade indices of public companies on Ventuals. Indices are organized by themes, such as the nuclear, semiconductors, robotics, and more. This allows traders to easily get exposure to a diversified group of companies that best capture an investment thesis.

### Get started

{% content-ref url="/pages/ENZTSSIr4QM2vI3ZaxEz" %}
[Broken mention](broken://pages/ENZTSSIr4QM2vI3ZaxEz)
{% endcontent-ref %}

{% content-ref url="/pages/odyrMqwRIjz8DrZgd6ZC" %}
[Markets](/overview/markets.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ventuals.com/overview/why-ventuals.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 `automate deployments from our CI pipeline` 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.
