> For the complete documentation index, see [llms.txt](https://docs.sigrex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sigrex.io/prediction-signal-bot-beta/create-prediction-signal-bot.md).

# Create Prediction Signal Bot

This page explains how to create and configure a bot that automatically executes trades on prediction markets (e.g. Polymarket) based on incoming webhook signals.

#### ⚠️ Early-stage limitation

> **Prediction Signal Bots are currently in an early stage of development.**
>
> At this time, Prediction Signal Bots can **only be triggered through** [**Bot Webhooks**](/getting-started/webhook.md). They cannot natively create or manage positions from Code Strategies, LLM Sessions, or other Sigrex strategy types.
>
> However, you can build integrations around this limitation. For example, a **Code Strategy** can send signals to a Prediction Signal Bot's webhook using [`$.Http.post()`](https://docs.sigrex.io/prediction-signal-bot-beta/pages/PpGEzbE7tbHdXWi3gkdn#usd.http), allowing you to trigger the bot programmatically from your own strategy logic.
>
> Native integration with Code Strategies, LLM Sessions, and other automation components may be added in future updates.

### 🧠 How It Works

A Prediction Signal Bot:

1. Listens to a **webhook endpoint**
2. Receives a **signal payload**
3. Executes trades on a connected **Prediction Market account**

***

### 📝 Configuration Fields

#### `Name` *(optional)*

A custom name for your bot.

* Example: `BTC 100K Strategy`
* If left empty, the bot will be named automatically based on the webhook URL

***

#### `Webhook` *(required)*

Select the webhook that will trigger this bot.

* This is the endpoint where your signals will be sent
* Must match the payload format described in the **Signal Payload** page

📌 You can connect:

* TradingView alerts
* Custom scripts
* External AI systems

***

#### `Frequency` *(optional but recommended)*

Controls how often the bot is allowed to execute trades.

* Example: `1 in every 1 second`
* Helps prevent:
  * Spam signals
  * Duplicate executions
  * Rate-limit issues

📌 If multiple signals arrive within the interval, only one will be executed.

***

#### `API Connection` *(required)*

Select your connected **Prediction Market account**.

* This is the wallet connection you created earlier
* Used to:
  * Sign transactions
  * Execute trades
  * Access your funds

***

#### **`Slug From Signal`**&#x20;

Enables Wildcard / Slug from Signal mode.

* Enabled → The bot dynamically processes market slugs provided in each incoming [signal payload](/prediction-signal-bot-beta/payload-format.md), allowing a single bot to trade multiple markets dynamically.
* Disabled → The bot only trades the fixed market specified in the Market URL field.

⚡ Performance Note: Because the market slug must be verified before each order execution, Wildcard mode is slightly slower than using a fixed slug. For bots designed to trade a specific market exclusively, keeping this toggle disabled is recommended.

#### `Market URL` *(*&#x72;equired if 'Slug From Signal' is disable&#x64;*)*

The full URL of the prediction market you want to trade.

* Example:

```
https://polymarket.com/event/elon-musk-of-tweets-april-2026/elon-musk-of-tweets-april-2026-840-879
```

📌 The system extracts the **slug** from this URL automatically.

***

<figure><img src="https://249033878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9eVrTushLZJUnDJcuAQG%2Fuploads%2FH7oQidcYCB6FPmStKIYL%2FScreezxzasfasnshot%202026-04-23%20125029.png?alt=media&amp;token=238481b6-1093-4330-9a90-1613cef78dcf" alt=""><figcaption></figcaption></figure>

#### ⚠️ Important — Slug Matching

The **slug in your** [**signal payload**](/prediction-signal-bot-beta/payload-format.md) **must match this market exactly**.

* From the URL above:

```
elon-musk-of-tweets-april-2026-840-879
```

* Your signal must include:

```
{
  "slug": "elon-musk-of-tweets-april-2026-840-879"
}
```

❗ If the slug does **not match**, the bot will ignore the signal.

💡 Tip:\
Always copy the market URL carefully — even small differences in the slug will prevent execution.

***

#### `Amount From Signal`&#x20;

Controls how trade size is determined:

* **Enabled** → Use `size` from incoming signal payload
* **Disabled** → Use fixed amount defined below

***

#### `Amount` *(required if 'Amount from Signal' disabled)*

The default trade size.

* Denominated in **USDC**
* Example: `250`

📌 This is used when:

* No `size` is provided in the signal
* Or "Amount From Signal" is disabled


---

# 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.sigrex.io/prediction-signal-bot-beta/create-prediction-signal-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.
