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

# What is the $ETHOS Token?

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

$ETHOS is the core of the Ethos DeFi ecosystem — a utility and rewards token designed to empower users, builders, and the community alike.

It’s not just a speculative asset. It’s a real utility token with real-world value backed by platform revenue, participation, and transparent economics.

Here’s what $ETHOS does:
\
• Earn rewards by staking, lending, or using Ethos products
\
• Save with discounts on borrowing, fees, and premium tools
\
• Unlock exclusive features through loyalty tiers
\
• Participate in governance and ecosystem decisions
\
• Support sustainability through buybacks and burns tied to real product activity

$ETHOS aligns everyone in the ecosystem — users earn for using, developers build for rewards, and the system grows sustainably over time.


---

# 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://token.ethos.io/what-is-the-usdethos-token.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.