> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/tokens/what-gives-sgage-a-bid.md).

# What gives sGAGE a bid

Liquidity demand, fee-funded bids, and the shape of the drip.

Selling pressure on sGAGE comes from unlocked rewards. Here is what meets it.

## Pool entry

Adding liquidity can create demand for sGAGE. Providers may buy it, use unlocked rewards or supply one-sided liquidity where the chosen range permits it.

## Deal fees

The entire 1% deal fee converts from USDG through ETH into GAGE and funds one-sided bids for sGAGE in the pool. It does not immediately buy and burn sGAGE. See [Deal fees and floor liquidity](https://docs.gage.cash/pool/buyback.md).

## The floor

Half of the launch's creator fees buy GAGE and park it as a standing bid for sGAGE just under the market. The bid thickens with every clip and ratchets up as the market rises. See [The sGAGE floor](https://docs.gage.cash/pool/the-floor.md).

## The drip

Rewards reach wallets a little at a time and mostly at the end of a term, so sell pressure arrives as a trickle against buyers who show up every week. See [The drip](https://docs.gage.cash/rewards/the-drip.md).

## The supply

Five billion, minted once, only ever decreasing. There is no team allocation, no treasury allocation and no mint function.

## The gauge

None of this promises a price. The pool price of sGAGE in GAGE is set by buyers and sellers alone. It is shown on the Protocol page's pool card, and the sGAGE burned this week under its More numbers, so the token's whole story is two numbers anyone can read.


---

# 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.gage.cash/tokens/what-gives-sgage-a-bid.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.
