# User Payment

When a user pays amount X, they are actually doing two separate things:

#### **1. Content Value Layer: Is this content worth paying for?**

This is the **consumption motivation**:

> **I recognize the value of this content and I’m willing to pay for it.**

* 20% of the payment goes to the creator as support — this is a direct value exchange.

The corresponding experience includes:

* The platform is fundamentally **paid-content-first**, not free content funded by ads.
* Clicking **“Like”** means the user is willing to **pay to support this content.**
* Clicking **“Dislike”** reduces similar content in the feed, allowing the information stream to quickly converge toward the user’s preferences.

#### **2. Prediction Market Layer: Will this content become popular?**

This is a mix of **gratitude + incentive + game motivation:**

> I think this content is great, and I want to thank the people who helped spread it to me.
>
> I can help push this piece to spread further and help make the prediction come true.
>
> Since it’s so good, more people will read it and tip it later. If I act now, I have a chance to share in juniors’ tips.

* This part corresponds to the 80% that flows into the **Senior Reward Pool.**
* It does not change the intrinsic value of the content, but instead builds a lightweight prediction market around:

“Who can spread better, see more clearly, and dare to act earlier?”


---

# Agent Instructions: 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:

```
GET https://docs.talex.world/talex-as-a-new-content-app/user-payment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.