> 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/deepdive/competitor-analysis.md).

# Competitor Analysis

If you're a content creator, Kaichi is the most cost effective solution to monetize your content.&#x20;

Here is a breakdown comparison of the commission rates across various platforms (most of them don't even have a social network associated with their platform):&#x20;

<table><thead><tr><th width="297">Content Creator Platforms</th><th>Commission Fees on Content Sales</th></tr></thead><tbody><tr><td>Kaichi</td><td><a href="broken://pages/5tqMO2ytaSCtS9eU9Qgh#fees">5%</a></td></tr><tr><td>YouTube</td><td><a href="https://support.google.com/youtube/answer/72902?hl=en#zippy=%2Cwhats-my-revenue-share">45% to 55%</a></td></tr><tr><td>Patreon</td><td><a href="https://support.patreon.com/hc/en-us/articles/11111747095181-Creator-fees-overview">8% to 12%</a></td></tr><tr><td>OnlyFans</td><td><a href="https://onlyfans.com/help/3/120/129">20%</a></td></tr><tr><td>Fansly</td><td><a href="https://fansly.com/application">20% </a></td></tr><tr><td>Substack</td><td><a href="https://support.substack.com/hc/en-us/articles/360037607131-How-much-does-Substack-cost">10%</a></td></tr></tbody></table>

**All these platform also charge an extra 2.9% fee on credit card payments.** \
\
But because Kaichi is using Solana, you pay no additional fee to receive the payments for your content sales, only a blockchain transfer of 0.000005 SOL (about $0.0007 USD).&#x20;


---

# 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/deepdive/competitor-analysis.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.
