> For the complete documentation index, see [llms.txt](https://documentation.script.tv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.script.tv/script-tokens/spay/spay-tokenomics/scriptglass-explained/economics.md).

# Economics

## Demand

The demand for the SPAY token has three compulsory drivers:

1\) Minting

2\) Recharging

3\) Buying gems

These three compulsory drivers are what the protocol calls mandatory burnable events, which will ensure that SPAY’s supply doesn’t inflate beyond control. One optional burnable event is purchasing recharge vouchers.

## Supply

The supply of SPAY tokens has one driver, i.e., payouts upon watching the content. These payouts are structured so that the user earns net positive SPAY each time they watch content, and at the same time, the protocol isn’t in a cumulative net loss. The supply is offset by burnable events, which are compulsory to execute if the user intends to earn by watching the content.


---

# 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://documentation.script.tv/script-tokens/spay/spay-tokenomics/scriptglass-explained/economics.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.