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

# Introduction

TL;DR: here is a 30sec video giving a high level overview of Kaichi: 

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

At Kaichi, we build tools that enable everyone to effortlessly take part in the new economy - an economy driven by tokenization and financialization, where decentralisation and digital ownership prevail.&#x20;

Social consensus, traditionally shaped on web2 platforms by a complex interplay of algorithmic decisions and user interactions, is at Kaichi influenced directly by market forces. Unlike conventional social networks that primarily focus on user engagement metrics, Kaichi introduces a dynamic marketplace where users actively participate in determining the value of content through the exchange of tokens.&#x20;

The market-driven social consensus on Kaichi transforms the platform into a dynamic marketplace of ideas and content.&#x20;

Furthermore, **we align financial incentives between creators and social media platforms**, and offer a fair governance framework as well as a censorship resistant environment for content creation. Key to understanding Kaichi is to consider it a free-market platform.&#x20;

Users can for example:

1. **Tokenise their social capital** by creating their own **supply-controlled token** and monetising their content.&#x20;
2. **Invest in the upside and growth of their favorite creators** by buying and selling the creator’s token depending on how much value the creator provides.
3. **Earn a share of the platform’s revenue** as a consistent cash flow stream from the fees that Kaichi earns, and also from the earnings of each tokens and memecoins that you hold.

<figure><img src="https://1532848985-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3CiOS7bcK0Alvva51mmv%2Fuploads%2F10y2hta5garOCglAv9el%2FGroup%2055602.png?alt=media&amp;token=cfd3fd34-2109-42bb-a068-5aa6b2b5ed60" alt=""><figcaption></figcaption></figure>

### Features

<div data-full-width="false"><figure><img src="https://1532848985-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3CiOS7bcK0Alvva51mmv%2Fuploads%2Ffv3xhLUacDnr2koaYpqX%2FFrame%2055513.png?alt=media&amp;token=b8e5d3c2-9831-448f-bd7a-fb622f9e0a2f" alt=""><figcaption></figcaption></figure></div>

With a decade of trading experience and backgrounds in traditional finance, the founders of Kaichi were clear in their design for the token stack: **transform creator tokens from pump-and-dump schemes into sustainable tokenized models** where both the creator, the token buyer (e.g., follower) and the platform benefit.

The solution is two-fold:

1. **Three token launch presets** are curated to cater to the needs of the creator, brand, or meme coin community. Each preset has its own distribution and, more importantly, its launch mechanism (market making). This guarantees a sustainable bootstrap phase for your token.
2. A **revenue-sharing model** is integrated into all transactions on the platform, powered by the platform's native token, $KAI.


---

# 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.kaichi.xyz/essentials/introduction.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.