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

# The Metronome Token ($MET)

Metronome’s native token ([$MET](https://etherscan.io/token/0x2Ebd53d035150f328bd754D6DC66B99B0eDB89aa), also referred to as MET) is an ERC-20 utility token. There are two primary use cases for the MET token.

* Governance: $MET can be locked in return for esMET, which is the governance token for the Metronome DAO. This will enable users to participate in governance proposals and voting.
* Revenue Share: By locking MET to receive esMET, participants earn a share of protocol revenue through revenue-backed MET buybacks, with rewards distributed proportionally based on the amount of esMET held.

Future and additional use cases for the MET 2.0 token are being explored. This document will be continually updated with the latest information.

<br>


---

# 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.metronome.io/metronome-synth/the-metronome-token-usdmet.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.
