> For the complete documentation index, see [llms.txt](https://midashand-1.gitbook.io/midaspredict/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://midashand-1.gitbook.io/midaspredict/knowledge-base/x-bot-midashandbot.md).

# X Bot (@midashandbot)

<figure><img src="/files/4p3RP7xfT260yZLzQaY8" alt=""><figcaption></figcaption></figure>

> 🐦 The **MidasPredict X bot** lets you check markets, prices, your positions, and your trading activity directly from X — just by @mentioning it in a tweet or reply.

The bot is live at [@midashandbot](https://x.com/midashandbot). It's read-only by design: ask anything about a market, your account, or what's hot on the platform, and get a structured reply in seconds. **Trade, redeem, and create-market commands ship with mainnet** (see [Actions](#actions-trade-and-manage-coming-in-mainnet) below).

***

### Setup <a href="#setup" id="setup"></a>

The bot answers based on your **linked X account**, so before it can respond to you, you need to connect your X handle to your MidasPredict profile:

1. Open **Profile → Settings → Account Access** on MidasPredict
2. Click **Connect X account**
3. Authorize the link in the X popup

Once connected, the bot recognizes your X handle as your MidasPredict wallet on the next mention. The link is one-time — you don't need to re-authorize for each command.

> ⚠️ **The bot only responds to mentions from connected accounts.** If you @mention it from an X account that hasn't been linked to a MidasPredict profile, the bot won't reply.

***

### How to Use <a href="#how-to-use" id="how-to-use"></a>

@mention the bot in any tweet or reply, followed by your command. The bot understands natural-language phrasings — you don't need to memorize exact syntax. Some examples:

```
@midashandbot what's trending right now?
@midashandbot status of Will Bitcoin reach $79,000?
@midashandbot my positions
@midashandbot help
```

The bot replies in the same thread, usually within seconds. If it doesn't understand your query, it'll reply with **"That didn't quite work. Reply with 'help' to see what I can do."**

![Help response](/files/8MEHtX52I1ELdvAjsKvE)

***

### Commands <a href="#commands" id="commands"></a>

#### Discovery — find markets <a href="#discovery--find-markets" id="discovery--find-markets"></a>

<table><thead><tr><th width="134">Command</th><th width="254">What it returns</th><th>Sample phrasings</th></tr></thead><tbody><tr><td><strong>Trending</strong></td><td>Top active markets, split into Boosted and Normal sections</td><td>"what's trending", "hot markets", "top markets right now"</td></tr><tr><td><strong>New markets</strong></td><td>Most recently created markets</td><td>"what's new", "latest markets", "latest 3 markets"</td></tr><tr><td><strong>Ending soon</strong></td><td>Markets closing today or this week</td><td>"ending soon", "closing today", "closing this week"</td></tr></tbody></table>

A trending reply looks like this — boosted markets surfaced first, then normal markets, with prices, volume, time-to-close, and the market URL on each:

![Trending markets reply](/files/GTlQqqDEU0JroxF3SP3z)

#### Market info — look up a specific market <a href="#market-info--look-up-a-specific-market" id="market-info--look-up-a-specific-market"></a>

<table><thead><tr><th width="116">Command</th><th width="274">What it returns</th><th>Sample phrasings</th></tr></thead><tbody><tr><td><strong>Status</strong></td><td>Full market details — outcomes, prices, TVL, volume, traders, dates</td><td>"status of &#x3C;market>", "info on &#x3C;market>", "tell me about &#x3C;market>"</td></tr><tr><td><strong>Odds</strong></td><td>Just the current outcome prices</td><td>"odds on &#x3C;market>", "what's &#x3C;market> trading at", "prices on &#x3C;market>"</td></tr><tr><td><strong>Rules</strong></td><td>Resolution criteria and sources</td><td>"rules for &#x3C;market>", "how does &#x3C;market> resolve", "criteria for &#x3C;market>"</td></tr><tr><td><strong>Holders</strong></td><td>Top 5 holders of YES (default). Add "No" for the NO side.</td><td>"top holders on &#x3C;market>", "whales on &#x3C;market>", "whales on &#x3C;market> No"</td></tr></tbody></table>

A **status** query returns the most complete picture of a single market in one reply:

![Market status reply](/files/EMMiLFhxd2xYH149t7l9)

Asking for **rules and holders** together returns both in one threaded reply:

![Rules + holders reply](/files/6xAfcl7IYXDNfAp9IOan)

#### Account — your data <a href="#account--your-data" id="account--your-data"></a>

These require a connected X account.

<table><thead><tr><th width="170">Command</th><th>What it returns</th><th>Sample phrasings</th></tr></thead><tbody><tr><td><strong>My profile</strong></td><td>Your volume, MP, markets created, active markets, join date</td><td>"my profile", "my stats", "how am I doing"</td></tr><tr><td><strong>My positions</strong></td><td>All your current outcome holdings, sorted</td><td>"my positions", "my holdings"</td></tr><tr><td><strong>My position on &#x3C;market></strong></td><td>Your specific holdings in one market</td><td>"my position on &#x3C;market>", "my shares on &#x3C;market>"</td></tr><tr><td><strong>My trades</strong></td><td>Your recent trade activity</td><td>"my recent trades", "my activity", "my last 10 trades"</td></tr><tr><td><strong>My markets</strong></td><td>Markets you created</td><td>"my markets", "markets I created"</td></tr></tbody></table>

Profile and positions look like this:

![My profile reply](/files/fPkBWAXUQIiX5Foz1DKH)

![My positions reply](/files/OOb4f3ezrYw2NqCTNgDy)

#### Help <a href="#help" id="help"></a>

`@midashandbot help` shows the full command list inline. Use it any time you forget the phrasings.

#### Actions — trade and manage 🗓️ *Coming in mainnet* <a href="#actions-trade-and-manage-coming-in-mainnet" id="actions-trade-and-manage-coming-in-mainnet"></a>

These commands let you trade, redeem winnings, and even create new markets directly from X. They're not yet live — they ship alongside mainnet launch.

<table><thead><tr><th width="144">Command</th><th width="262">What it does</th><th>Sample phrasings</th></tr></thead><tbody><tr><td><strong>Buy</strong></td><td>Open a position on YES or NO at the current price</td><td>"buy 10 USDC on Yes &#x3C;market>", "buy 50 USDC on No &#x3C;market URL>"</td></tr><tr><td><strong>Sell</strong></td><td>Close all or part of a position</td><td>"sell all on No &#x3C;market>", "sell 100 shares on Yes &#x3C;market URL>"</td></tr><tr><td><strong>Redeem</strong></td><td>Claim winnings from a resolved market</td><td>"redeem &#x3C;market title or url>"</td></tr><tr><td><strong>Create market</strong></td><td>Open a new market on a topic</td><td>"create market about &#x3C;topic>"</td></tr></tbody></table>

***

### Tips <a href="#tips" id="tips"></a>

* **Be specific with market names.** The bot matches by partial name, but ambiguous queries can fail. If the wrong market comes back, retry with the full title or paste the market URL directly.
* **Follow-ups work in the same thread.** If your last command was about a specific market, the bot remembers it for short follow-ups like "what about the rules?" or "and the holders?".
* **No private info in mentions.** Bot replies are public tweets. Don't ask for anything sensitive — your profile data is what anyone could find by looking at your wallet, but it's still visible to everyone who sees the thread.
* **Combine up to 3 commands in one mention.** "@midashandbot trending, new markets, and ending soon" returns all three in a single reply. Beyond 3, send the rest as a follow-up.

***

### What the bot can't do <a href="#what-the-bot-cant-do" id="what-the-bot-cant-do"></a>

* **Place trades, redeem, or create markets** — these ship with mainnet (see [Actions](#actions-trade-and-manage-coming-in-mainnet) above). On testnet today, the bot is read-only for fund-moving actions.
* **Resolve markets, dispute outcomes, or change your settings** — outside the bot's scope; use the app for these.
* **Reply via DM** — only mentions in public tweets are answered.

To trade, dispute, or change settings, open the linked market or your profile on [midashand.xyz](https://midashand.xyz/) and act there.

<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://midashand-1.gitbook.io/midaspredict/knowledge-base/x-bot-midashandbot.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.