> For the complete documentation index, see [llms.txt](https://yvechat.gitbook.io/wp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yvechat.gitbook.io/wp/yve/revenue.md).

# Revenue

YveChat generates revenue from software, tooling, and network participation, with the inference bill left entirely to the user and their provider.

***

### Revenue Streams

| Stream                 | Who pays                                                      | What they pay for                                                        |
| ---------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Scaling Tier**       | Individuals and teams whose work outgrows one machine         | Extended agents, team workspaces, encrypted sync, priority builds        |
| **Gateway Usage**      | Users routing tools through YveChat-operated providers        | Search, extraction, and reading calls carrying real marginal cost        |
| **Deployment Support** | Organizations running self-hosted YveChat                     | Provisioning assistance, runbooks, upgrade support, response commitments |
| **Marketplace Take**   | Builders selling agents, prompt packs, and MCP configurations | A defined share of marketplace transactions                              |

Payment is accepted in fiat or `$YVE`. A portion of fiat revenue is recycled into token buybacks, aligning contributors with adoption.

***

### Upcoming Expansions

The workspace remains the foundation. From it, further layers of value open.

| Stream                   | Who pays                                               | What they pay for                                                    | Why it matters                                                                     |
| ------------------------ | ------------------------------------------------------ | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **Compute Network**      | Users choosing to route inference to network operators | Served inference, settled in `$YVE`                                  | Turns idle GPU capacity into supply and gives operators a reason to hold the token |
| **Engine Operator Tier** | Operators running high-availability Engines for teams  | Enhanced monitoring, failover, and multi-user pairing                | Extends custody to organizations without moving data to us                         |
| **Verified Agents**      | Builders seeking distribution                          | Review, signing, and placement for agents meeting security standards | Creates a trust layer where a marketplace would otherwise carry risk               |

***

### What Is Never a Revenue Stream

Stated explicitly, because the exclusions define the position more sharply than the inclusions.

| Excluded                    | Reason                                                                                                |
| --------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Margin on inference**     | Permanent commitment. The user pays their provider directly at the provider's price                   |
| **User data**               | Conversations never reach YveChat infrastructure, which makes monetizing them structurally impossible |
| **Training access**         | There is no corpus to sell                                                                            |
| **Advertising**             | Placement inside a reasoning surface corrupts the reasoning                                           |
| **Model routing kickbacks** | Provider neutrality holds only while no provider is paying for preference                             |

***

### Alignment

```mermaid
graph LR
    R["Fiat revenue"] -->|"portion"| BB["Buybacks"]
    BB --> T(("$YVE"))
    T --> H["Holders and operators"]
    H -->|"build and serve"| N["Network capacity"]
    N --> U["Users"]
    U --> R
```

Revenue grows with adoption of custody. That is the alignment the position requires: YveChat earns more when more people hold their own keys, and earns nothing from how much they think.

***

{% hint style="warning" %}
Revenue streams described here are planned. No stream is claimed as operating today. See [Disclaimer](/wp/resources/disclaimer.md).
{% endhint %}

***

Money enters through software.

It never enters through your prompts.


---

# 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://yvechat.gitbook.io/wp/yve/revenue.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.