# ASK Tokenomics

ASK is the native token powering the Permission ecosystem. \
\
It underpins how value flows across the platform — aligning incentives between individuals, families, AI agents, and the broader Permission Protocol.\
\
ASK enables permissioned participation, agent-to-agent (A2A) value exchange, and long-term ecosystem alignment. Over time, it will also support governance and staking.

ASK is omnichain via LayerZero’s OFT standard, meaning it flows across the chains that power Permission (currently, Base and Polygon), with additional chains planned as the ecosystem expands.

### **A Closed-loop flywheel**

As Permission’s family-focused products scale, **subscription revenue** generated from parents using the platform is used, in part, to **buy back ASK from the open market**.

These buybacks:

* Create sustained, non-speculative demand for ASK
* Align long-term holders with product adoption
* Reinforce ASK’s role as permission and incentive infrastructure

ASK acquired through buybacks is used to **fund rewards and incentives** across the Permission ecosystem — particularly in family contexts where ASK is used to motivate, reinforce, and reward positive behaviors.

This creates a flywheel where:

1. Parents subscribe to Permission products
2. Subscription revenue funds ASK buybacks
3. ASK is used to power rewards and incentives
4. Increased ASK utility reinforces demand
5. The cycle repeats as adoption grows

### Supply Allocation

**Total Supply**: 100 billion ASK (fixed, uninflatable). \
\
Below is a breakdown of ASK’s total token supply, including allocations for growth, contributors, and ecosystem participants.\
\
These allocations are designed to incentivize long-term participation and value creation across the Permission network.

<figure><img src="/files/Uu1px256fut5wRtfITAX" alt=""><figcaption></figcaption></figure>

### Unlock Schedule

ASK follows a long-term unlock schedule designed to:&#x20;

* Align incentives across stakeholders
* Support sustainable ecosystem growth

You can view real-time supply data via our API:

* Total supply: `https://api.permission.io/v1/token/supply?q=total`
* Circulating supply: `https://api.permission.io/v1/token/supply?q=circulating`

The unlock schedule may adjust over time in response to governance decisions or strategic platform evolution.

<figure><img src="/files/SCAFe0GzYSmEL9XvtJnz" alt=""><figcaption></figcaption></figure>

### ASK Utility & Use Cases

ASK has multiple, reinforcing utilities across the Permission ecosystem:

#### **Family Rewards & Incentives**

ASK is used by parents as a flexible reward mechanism to:

* Incentivize positive behaviors
* Reinforce habits, learning, and responsibility
* Support goal-setting and value-aligned motivation within families

This use case represents a core demand driver for ASK as family adoption scales.

#### **Agent-to-Agent (A2A) Value Exchange**

ASK powers value exchange between AI agents operating within the Permission Protocol.

As agents negotiate, coordinate, and transact on behalf of humans, ASK serves as the native medium for permissioned, auditable A2A interactions.

#### **Protocol Participation & Governance**

ASK holders will be able to participate in governance decisions related to the Permission Protocol, including:

* Platform parameters
* Incentive mechanisms
* Ecosystem evolution

#### **Staking & Yield (Future)**

ASK is expected to support staking and other participation-based mechanisms over time, designed to:

* Encourage long-term alignment
* Support protocol security
* Reward active ecosystem contributors

Trusted One-to-One Relationships™


---

# 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.permission.ai/ask-token/ask-tokenomics.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.