> 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/utility.md).

# Utility after launch

How $LENS works inside the product once it launches, without ever gating a call.

{% hint style="info" %}
Planned design. These uses switch on only after launch, and each will be reviewed by securities counsel before it ships.
{% endhint %}

Every use of $LENS below is tied to something the LensAI network already does. One rule holds across all of them: **calls, briefs, the record and the evidence stay free and identical for everyone.** Holding or staking $LENS changes how much of the desk's capacity you can use and how you take part in it. It never changes what the desk concludes.

## 1. Business access

Businesses are the paying side of LensAI (see [Economics](/business/economics.md)). After launch, every business line can be paid in $LENS as well as in stablecoins, with a better rate when paid in $LENS:

* **API and MCP volume** above the free cap, for platforms and agents that build on the engine;
* **Team desks:** shared watches, alerts routed to team channels, higher budgets and an audit trail;
* **Data licensing:** point-in-time access to the cross-factor history, the corpus and the calibration record;
* **Partner widgets** at scale.

## 2. Capacity staking

Free research has fair daily caps, so the desk is not farmed by bots. Staking $LENS raises **capacity**, never access to conclusions:

| Stays free for everyone               | Raised by staking                                       |
| ------------------------------------- | ------------------------------------------------------- |
| Every call and every no call          | Daily deep reads and specific questions                 |
| Shared Market State and token briefs  | Number of active watches                                |
| The public record and scorecards      | Watch evaluation priority and alert channels            |
| Every evidence block behind an answer | Claim checks per day                                    |
| What changed                          | API rate limits and deeper history windows over the API |

Staked tokens are locked, not spent. Staking tiers are published and identical for everyone.

## 3. Coverage governance

Holders steer **what the desk covers**, never what it concludes:

* **The coverage queue:** which assets, perpetual markets and venues are added next;
* **Data spending:** treasury proposals to license or add data sources, such as cross-venue liquidations, ETF flows or on-chain token structure;
* **Mechanism proposals:** new channels for the mechanism graph, proposed by holders and admitted only after review by the curators against documented mechanics;
* **The tone arena:** votes between blunt and balanced versions of real reads, with the results published.

Governance cannot vote on a call, force a call or a no call, remove a miss from the record, change the scorecard, or lift the rule against calls on $LENS and related tokens.

## 4. Contributor rewards

The community allocation rewards **verified contributions**, not raw usage, so that rewards cannot be farmed:

* **Mechanism bounties:** a proposed graph channel that the curators accept;
* **Incident evidence:** primary-source evidence that is used in an Incident Mechanics brief;
* **Claim reports:** viral claims submitted for checking that turn out to be material;
* **Corrections:** a verified error found in the desk's data or output;
* **Security and bug bounties** for the engine, the API and the MCP server;
* **Open research:** benchmark cases, evaluations and translations of the record.

Rewards are Sybil-filtered, published, and vest on the community schedule.

## 5. Settlement between agents

When outside agents use LensAI's tools at volume, $LENS can settle those calls directly, agent to agent, over open payment standards for machine payments. Claim Check as a paid "verify before act" service for trading agents is the clearest case: an agent pays a small amount to check a number before acting on it. This switches on only when real agent demand exists; until then, agent access stays free up to its cap.

## 6. A distribution to real users

Part of the community allocation is distributed to **real users of the desk**, measured from the product's own records and filtered against bots and duplicate accounts. It rewards the people who used and tested LensAI before the token existed, and it does not require buying anything.

## What $LENS is not for

* It is not required to use LensAI, to read a call, or to see the record.
* It does not buy a different call, an earlier call or a private call.
* It is not a claim on LensAI's revenue, and it carries no promise of value.


---

# 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/utility.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.