> For the complete documentation index, see [llms.txt](https://liber-coin.gitbook.io/liber-coin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://liber-coin.gitbook.io/liber-coin/fixed-apy.md).

# Fixed APY

**APY** stands for Annual Percentage Yield. This measures the real rate of return on your principal amount by taking into account the effect of compounding interest. In the case of Liber, your $LIBER tokens represent your principal, and the compound interest is added periodically on every Rebase event (Every 15 minutes), otherwise known as an 'Epoch'. Your new principal amount is your then current Liber token amount, plus your new rebase token amount. This total amount is what gets calculated for your next rebase rewards. \
**The Power of Compound Interest** - It is important to note that your balance will grow not linearly but exponentially over time. \
Taking a compound interest of 0.03466% / 15 minutes.


---

# 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://liber-coin.gitbook.io/liber-coin/fixed-apy.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.
