> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/blockchain/learn-iotex/wallets/supported-wallet-apps/rabby-wallet.md).

# Rabby Wallet

Rabby Wallet offers a seamless and straightforward UI to engage with your assets, thanks to its native integration of the IoTeX Blockchain. This means that users do not need to undergo any additional configuration steps to manage their IOTX tokens, track their staked IOTX balance, participate in staking, or interact with IoTeX's decentralized applications (DApps). 

{% hint style="success" %}
Its intuitive design and native integration with IoTeX make Rabby Wallet an excellent alternative to more generalist wallets like Metamask.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/EyawgxYexImpo6OGzEiR/blobs/MH2I5BGaDohjncMySTUk/image.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
For those ready to dive into the IoTeX ecosystem with Rabby Wallet, the next step is simply downloading the application.

-> Visit the [Rabby Wallet download page](https://therabbit.io) to get started.&#x20;
{% endhint %}


---

# 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.iotex.io/blockchain/learn-iotex/wallets/supported-wallet-apps/rabby-wallet.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.