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

# X Bot

Trade prediction markets, create your own, redeem winnings, and check the action — all by tweeting at Limelight. The X (Twitter) bot is **@AskLimelight** ("Limelight ◆ tweet to trade", automated by **@Limelight\_Preds**). Mention it in plain language, say what you want, and it replies in your thread.

> Profile: [x.com/AskLimelight](https://x.com/Asklimelight). Trades settle in **USDCx** on Movement and are **non-custodial** — the bot never holds your keys, and every trade waits for your confirmation.

### How It Works <a href="#how-it-works" id="how-it-works"></a>

* **@mention the bot.** Your tweet is the command — e.g. *"@AskLimelight buy 10 USDCx YES on \<market>"*. It replies in the same thread.
* **Natural language.** No exact syntax: *"ape 50 into YES on the Lakers market"* works like *"buy 50 USDCx YES on …"*. An AI parser reads your intent.
* **Threads carry context.** Follow-ups in the same thread continue the flow; if a thread goes quiet for a while, just start a new one.
* **Link your X account first.** On [limelight.markets](https://limelight.markets/), open **More → Profile Settings → Account Access** and link your **X** account (via Privy). Info queries work without linking; trading and your-account commands need it.

### Pointing at a Market <a href="#pointing-at-a-market" id="pointing-at-a-market"></a>

When a command needs a specific market, refer to it by a **link**, its **on-chain address** (`0x…`), or a **title phrase** — never a bare number (numbers are always amounts, share counts, or fees). After the bot shows a numbered list, you can also say *"the second one"* or *"buy 10 yes on the third"* and it resolves that item.

### Ask the Bot <a href="#ask-the-bot" id="ask-the-bot"></a>

| Say                               | You get                                                |
| --------------------------------- | ------------------------------------------------------ |
| `trending` / `what's hot`         | 🔥 Top active markets                                  |
| `new markets` / `what's new`      | ✨ Recently created markets                             |
| `ending soon` / `closing today`   | ⏰ Markets closing soon (next 24h or 7 days)            |
| `odds on <market>`                | 📊 Current prices / implied probabilities              |
| `status of <market>`              | 📊 Full market detail (prices, volume, expiry, status) |
| `rules for <market>`              | 📋 How the market resolves, with sources               |
| `my profile` / `how am I doing?`  | 👤 Your aggregated portfolio stats                     |
| `my position on <market>`         | 📊 Your holdings on that one market                    |
| `my positions` / `what do I hold` | 📊 Your full holdings list                             |
| `what can I claim` / `my wins`    | 🏆 Your redeemable winnings (list only)                |
| `my trades`                       | 📜 Your recent trades                                  |
| `my markets`                      | 🏪 Markets you created                                 |
| `help`                            | 🤖 Everything the bot can do                           |

### Tell the Bot To <a href="#tell-the-bot-to" id="tell-the-bot-to"></a>

| Say                                            | What happens                                                 |
| ---------------------------------------------- | ------------------------------------------------------------ |
| `buy <amount> USDCx <outcome> on <market>`     | 📋 Shows a review, then buys after you confirm               |
| `sell <shares or "all"> <outcome> on <market>` | 📋 Shows a review, then sells after you confirm              |
| `redeem <market>`                              | 💸 Claims your winnings from one settled market              |
| `create market about <topic>`                  | Drafts the market with AI for you to review, then submits it |
| `cancel`                                       | Drops whatever command is in progress                        |

> **Selling is sized in shares, not dollars.** *"sell 10 on No"* means **10 shares**; *"sell all"* closes your whole position. Buying is sized in **USDCx**.

## Trading Is Always Confirmed

Every **buy** and **sell** shows a **review** first — the market, your outcome, and the amount — and only sends the on-chain transaction after you reply **`yes`** (the bot also understands **`confirm`**). Reply **`cancel`** to drop it, or just tell it what to change.

* **USDCx only.** Trades settle in USDCx; fund your balance first (see [Wallets & Networks](/limelight-docs/knowledge-base/wallets-and-networks.md)).
* **Minimum buy is $0.10**; no minimum to sell.
* The trade is **re-priced when you confirm**, and you get a [**Movement Explorer**](https://explorer.movementnetwork.xyz/?network=mainnet) transaction link when it lands.
* **No trade advice.** Ask the bot whether to buy and it shows you the odds and rules, then leaves the call to you.

```
You:  @AskLimelight buy 50 USDCx YES on https://limelight.markets/markets/0xabc…

Bot:  📋 review BUY:
      📌 Will BTC hit $150k by Dec 31, 2026?
      🎯 YES · 💰 $50.00 USDCx
      reply 'yes' to confirm · 'cancel' to abort

You:  @AskLimelight yes

Bot:  🟢 bought!
      📌 Will BTC hit $150k by Dec 31, 2026? · 🎯 YES
      💰 50.00 USDCx @ $0.62 · 📦 80.65 shares
      🔗 tx → explorer.movementnetwork.xyz/txn/0x…
```

### Creating a Market by Tweet <a href="#creating-a-market-by-tweet" id="creating-a-market-by-tweet"></a>

Say *`create market about <topic>`*. You provide the **topic**, **seed liquidity** (minimum **$100** USDCx), your **creator fee** (**0–2%**), and a **cover-image link** (paste an http(s) URL). The bot's AI auto-drafts the rest — title, outcomes, resolution rules, sources, and category — and shows you a **draft to review**; reply **`yes`** to submit (or `edit <field> <value>` to change something). It goes to **review (\~24h)**, then live on-chain with your seed.

> **Creating a market is single-intent** — it can't be combined with other commands in the same tweet.

> **Creation access** follows the website: open to everyone for about the first month after launch, then gated to [Limelight Catalyst](/limelight-docs/for-creators/limelight-catalyst.md) holders.

```
You:  @AskLimelight create a market about ETH hitting $5k, seed 500, fee 1.5%, https://i.imgur.com/eth.png

Bot:  🤖 here's the AI-drafted market — review and tell me what to change:
      📌 Will ETH hit $5,000 by Dec 31, 2026?
      🎯 Yes / No · ⏰ Expires 2026-12-31 · 🏷️ CRYPTO
      📋 Resolution rules + sources filled in
      💰 Seed 500 USDCx · 💸 fee 1.5%
      reply 'yes' to submit for review (24h) · 'cancel' to abort

You:  @AskLimelight yes

Bot:  📨 submitted for review! once approved, it goes live on-chain with your 500 USDCx seed.
```

### Do Several Things in One Tweet <a href="#do-several-things-in-one-tweet" id="do-several-things-in-one-tweet"></a>

You can pack **up to three** requests into one mention — for example *"what's trending and what do I hold?"* or *"odds and rules on the BTC market."* Limits: at most **one trade** (buy or sell) per tweet, and **create** and **redeem** each have to go in a tweet of their own.

### Identity & Safety <a href="#identity--safety" id="identity--safety"></a>

* **You link your X account via Privy** on the website; the bot only ever acts within your own linked Limelight account.
* **You stay in control.** The bot never holds your keys, and every trade waits for your **`yes`**.
* **Real USDCx, non-reversible.** Trades and redemptions settle on-chain.
* **Injection-resistant.** The parser only classifies your intent — it never runs instructions buried in tweet text, and the bot stays focused on prediction markets. Never share your keys or seed phrase with anyone.


---

# 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://limelight-1.gitbook.io/limelight-docs/knowledge-base/x-bot.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.
