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

# Value flow

How business revenue, the treasury and the token relate.

{% hint style="info" %}
Planned design. Shares and mechanisms are illustrative until launch and subject to counsel review.
{% endhint %}

Revenue comes from businesses: API and MCP volume, team desks, data licensing and partner integrations. It flows in a fixed order:

1. **The pipeline first.** Live data, licensed feeds, model calls and infrastructure: the real cost of keeping the desk running and free for readers.
2. **The treasury next.** A published share of business revenue goes to the treasury, which funds coverage expansion, data sources, audits and grants under governance.
3. **Buybacks only by rule.** If the treasury buys back $LENS, it does so only from realised business revenue, under a published rule, never from token sales and never at discretion. Every buyback is reported net of the unlocks in the same period, so the supply picture is honest.

## Supply honesty

Buybacks are only meaningful when they are set against unlocks. Each quarterly report will show, side by side:

* tokens unlocked in the period, by allocation;
* tokens bought back, with the revenue that funded them;
* the net change in circulating supply.

## What does not happen

* No revenue share, dividend or yield is paid to holders.
* No buyback is funded by selling tokens or by the free product's budget.
* No figure in this paper is a projection of price or return.


---

# 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.scanbylens.xyz/business/token/value-flow.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.