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

# The $LENS token

Status, purpose and design of the $LENS token.

{% hint style="warning" %}
**Status: not launched.** There is no liquidity pool, no listing and no sale. Everything in this section describes a planned design for transparency. All figures may change before any launch. Nothing here is an offer to sell or a solicitation to buy any token, a promise of value, or financial advice.
{% endhint %}

## Why the token waits

LensAI's first job is to prove that its calls hold up in public. A token launched before that proof would put a price chart in front of a scorecard that does not exist yet. So the order is deliberate:

1. **Product first.** Free calls, a public record, monthly scorecards.
2. **Proof next.** Months of unbroken, scored calls, misses included, and real usage.
3. **Token last.** Launched only when it has a job the product needs, and only after securities counsel review and an independent audit.

## Design principles

* **Calls and research stay free.** The token never gates a call, a brief, the record or the evidence behind them. Everyone gets the same call whether they hold $LENS or not.
* **A job a stablecoin cannot do.** Every use of $LENS is tied to something the network does: capacity, coordination, contribution or settlement between agents. If a stablecoin would do the job equally well, it is not a reason for the token.
* **No calls on $LENS.** The desk will never make a call on $LENS, by design and in code.
* **Fixed supply.** One billion tokens, minted once, with no emissions, no mint function, no transfer tax and no owner privileges.
* **Public vesting.** Every allocation vests on a published schedule, enforced by public on-chain vesting streams, so no insider unlocks ahead of the community and no schedule can be shortened after the fact.
* **No profit language.** $LENS is a utility and coordination token. It is not a share, not a claim on revenue and not an investment product.

## In this section

* [**Supply, allocation and vesting**](/business/token/supply.md): the full tokenomics and circulating supply over time.
* [**Utility after launch**](/business/token/utility.md): how $LENS is used inside the product once it exists.
* [**Value flow**](/business/token/value-flow.md): how business revenue, the treasury and the token relate.
* [**Safeguards**](/business/token/safeguards.md): conflict rules, disclosure and what the team will never do.


---

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