> For the complete documentation index, see [llms.txt](https://powerfan-1.gitbook.io/redchat.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://powerfan-1.gitbook.io/redchat.app/faq/faq-monetization-visibility.md).

# Monetization & Visibility

We've gathered the questions we get asked most often about whether you can earn money with your characters, and how to get them in front of more people. Read through it at your own pace and it'll click in no time!

***

## Q1. Can I make money with the characters I create?

Yes, you can! It works through the **Referral** feature.

**Here's how it works:**

1. Hit the **Share** button on a character's profile to generate a share link.
2. **Even people who aren't logged in** can open this link, so you can show your character to newcomers without any friction.
3. When someone signs up and pays through your referral link, you receive **30% of what they pay for a full year (12 months)**.

> 💡 **Try it like this** Post your share link wherever your character would fit in — social media, Discord, your blog, and so on. People who love your character will sign up naturally, and that turns into referral earnings for you.

You can find the full details — referral rates, family referral, and more — in the [Referral Program](/redchat.app/policies/referral-program.md).

***

## Q2. Who earns the revenue from a share link — the creator, or the person who shared it?

Here's the gist, plain and simple.

* **💰 The person who earns the referral revenue = the person who shared the link** When a new user signs up and pays through a link you shared, the referral revenue goes **to you, the one who shared it**. It doesn't have to be a character you made yourself.
* **✨ The person who made the character = an indirect benefit** The more your character gets shared around, the more **exposure and fans** it gains. The direct referral revenue goes to whoever shared the link, but the creator clearly benefits too, since the character becomes more widely known.

> 📌 In one line: **the revenue goes to "whoever shared it,"** while the creator gains the **indirect benefit of "exposure and popularity."** And of course, if you share your own character yourself, you get both at once!

See the [Referral Program](/redchat.app/policies/referral-program.md) for the full breakdown of rates and the family referral system.

***

## Q3. To get more exposure — is a Story better, or individual Chats?

**We recommend grouping them into a Story!**

A **Story** gets **priority exposure** in the Feed and Explore. It stands out far more than individual Chats scattered around on their own.

So if you have Chats that relate to one another, gathering them **into a single Story** rather than leaving them apart works better for exposure.

> 💡 **Give this a try** Organize connected Chats — like "the same world," "continuing episodes," or "different scenes of the same character" — into a single Story. It makes the flow easier to follow for readers, and it also gets surfaced better by the algorithm.

> 🌱 **Not sure where to start?** Exposure ultimately starts with "a great character + a well-organized Story." Most of a character's appeal comes from the **Description**, so build your character on a solid foundation first → then bundle related Chats into a Story. → [Quick Creation](/redchat.app/guides/quick-creation.md) · [Advanced Creation](/redchat.app/guides/advanced-creation.md)

***

### Still have questions?

Reach out anytime via our support chat (bottom-right of your screen). We'll be glad to help you out quickly! 😊


---

# 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://powerfan-1.gitbook.io/redchat.app/faq/faq-monetization-visibility.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.