> For the complete documentation index, see [llms.txt](https://kodi.gitbook.io/kodi-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kodi.gitbook.io/kodi-whitepaper/about-us/our-vision.md).

# Our Vision

### Mission Statement

Kodi’s mission is to create a one-stop-shop IDO platform and provide investors with an interactive Entertainment Network that will keep users engaged, informed, and entertained while investing in the crypto space.

### Clear Vision

Our vision is to create an ecosystem that will be a driver in promoting a safer economic environment for crypto investors to participate in and for developers to grow their projects.

Kodi is creating an industry-first Entertainment Network that will become **THE** place for crypto investors to socialize, have fun, win prizes, and learn about everything crypto.

The Pitch Advertising Agency and CookieSale launchpad will work in unison to become the go-to destinations for developers to build their brands and launch their projects.

### Introducing Kodi

{% embed url="<https://www.youtube.com/watch?v=UifPOz_rRxU>" %}


---

# 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://kodi.gitbook.io/kodi-whitepaper/about-us/our-vision.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.
