> For the complete documentation index, see [llms.txt](https://docs.tenderize.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tenderize.me/introduction/tender-tokens.md).
# Tender Tokens
**Tender Tokens** are liquid staked tokens that automatically stake to a diverse set of high-performing validators, managed and curated by the Tenderize protocol and $WAGYU token holders. They allow users to easily stake and diversify without having to keep track of validator performance. \
\
Tender Tokens take into account network health and have rules to ensure healthy stake distribution across PoS networks. The rebalancing happens automatically on a smart contract level. New deposits are staked to the most underallocated validators, while withdrawals are processed from the most overallocated validators.
Similar to Liquid Delegations, Tender Tokens can still be unstaked regularly at no fee while waiting for the unstaking period of the underlying PoS network. But you can also instantly unstake them for a small fee. \
\
**A major difference** with liquid delegations is that Tender Tokens are **non-rebasing**, and instead use a floating exchange rate to indicate how much tokens the LST is worth (e.g. 1 tLPT = 1.20 LPT).\
\
These new LSTs are a perfect example of composability, creating a staking pool that uses various [Liquid Delegations](/introduction/liquid-delegation.md) under the hood with a set of allocation rules. Theoretically, anyone can create Tender Tokens with their own composition and rules, as the Tenderize protocol is fulle open for anyone to build on.
---
# 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://docs.tenderize.me/introduction/tender-tokens.md?ask=&goal=
```
`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.