> For the complete documentation index, see [llms.txt](https://docs.oomerbot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oomerbot.xyz/telegram-bots-info/oomer-bot.md).

# Oomer Bot

{% embed url="<https://t.me/OomerBot>" %}

## Tutorial

### How to create a wallet

Create an Oomer wallet by simply doing the following:

1. **Open Telegram**
2. **Open a chat with Oomerbot (**  [**https://t.me/OomerBot**](https://t.me/OomerBot) **)**
3. **Type /start**

This will automatically generate an Oomer wallet for your associated telegram user id and your Oomer interface appears.

<figure><img src="https://219160362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKCt8Ej9comaBXz9rx2ql%2Fuploads%2FCBNOSstS6GzOd43xIcdA%2Fimage.png?alt=media&amp;token=0ae4b556-3c22-4a38-90e2-99204bbb07df" alt=""><figcaption></figcaption></figure>

As you can see your Ethereum address is displayed. **Also, do not forget to write down your private key!** You can view your private key by clicking **"Reveal Private Key** �&#xDD11;**".**&#x20;

For this tutorial we are going to be clicking ***"Open Wallet*** �&#xDE80;***"***.

<figure><img src="https://219160362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKCt8Ej9comaBXz9rx2ql%2Fuploads%2FVnuctf0mGP86EiEC3qD0%2Fimage.png?alt=media&amp;token=832fce38-6cb4-48d1-a00f-468e8df3c1fc" alt=""><figcaption></figcaption></figure>

Most of this is self-explanatory. However, for the more important features I will be have subsections to explain these in more detail. You can find these subsections at the bottom of the page.

Buttons:&#x20;

* **Deposit** 💸- Replys with a QR code to deposit to your account and shows your address
* **Withdraw**🧾 - Withdraw ETH, ERC20 Tokens, or unwrap ETH.
* **Token Balances** 📊- A summary of your trading history and your ERC20 Token balances.
* **History** 📜- All transaction hashes you have made in the past few days.
* **Volumebot** 🤖- Links to the [volume bot](https://t.me/OomerVolumeBot).
* **Gamblebot** 🎰- Links to the [gamble bot](https://t.me/OomerGambleBot).
* **$OOM Token** 🪙- Allows users to exchange their $OOMER for $OOM.
* **Rev Share Stats** 💸- Shows your current revshare from other users.

For buttons: **"Swap | DCA" , "Launchpad", "Airdrop"** have their own subsections that are more detailed so please continue to each section to understand how to fully utilize Oomerbot.

{% content-ref url="/pages/wV8jcs5fSQF88oRY4ew6" %}
[Trade](https://docs.oomerbot.xyz/telegram-bots-info/oomer-bot/trade.md)
{% endcontent-ref %}

{% content-ref url="/pages/Tx2XUjRtuFvaAHSFt2dd" %}
[Airdrop](https://docs.oomerbot.xyz/telegram-bots-info/oomer-bot/airdrop.md)
{% endcontent-ref %}

{% content-ref url="/pages/QWEZsX4udRhCoJ8vHg7t" %}
[Launchpad](https://docs.oomerbot.xyz/telegram-bots-info/oomer-bot/launchpad.md)
{% endcontent-ref %}


---

# 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.oomerbot.xyz/telegram-bots-info/oomer-bot.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.
