Ctrlk
Dashboard
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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. 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(), 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

Enables Wildcard / Slug from Signal mode.

  • Enabled → The bot dynamically processes market slugs provided in each incoming signal payload, 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 (required if 'Slug From Signal' is disabled)

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

  • Example:

📌 The system extracts the slug from this URL automatically.

⚠️ Important — Slug Matching

The slug in your signal payload must match this market exactly.

  • From the URL above:

  • Your signal must include:

❗ 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

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

PreviousConnect Wallet
NextPayload Format

Last updated