Overview

Understand what Polyscout does and how it fits into your system.

What You Are Integrating

The Polyscout HTTP API exposes the same automation engine that powers the Polyscout Telegram bot. It allows external platforms such as bots, trading terminals, or backend services to create and manage automated Up or Down trading strategies on Polymarket without re-implementing execution logic.

All strategies created through the API are executed by Polyscout’s backend. Polyscout continuously monitors Polymarket odds and market conditions, determines when entry or exit conditions are met, and submits trades on behalf of the configured wallet.

The API is versioned under /v1, uses JSON for all requests and responses, and is authenticated using per-builder API keys. API keys are issued through the Polyscout Telegram bot using the /api command and are tied to a specific Polyscout builder account.

Strategy Scope

Strategies are always scoped to a wallet. A single builder can register multiple wallets, and each wallet can run multiple strategies. Polyscout maintains state per wallet and per strategy, including open positions, execution counts per event, and the most recent action taken.

Execution Loop

When a strategy is active, Polyscout evaluates entry and exit conditions in real time.

When an entry condition is met, Polyscout constructs the required Polymarket CLOB order payload, requests a signature from the configured signing endpoint for the wallet, and submits the signed order to Polymarket.

When an exit condition is met, such as a take profit or stop loss, Polyscout constructs the exit order, requests a signature, submits it, and updates the strategy state accordingly.

This same execution loop is used throughout the entire strategy lifecycle. Your system is only responsible for signing approved payloads. All market monitoring, decision logic, and order submission are handled by Polyscout.

Wallet Custody and Signing

Wallet custody remains fully under the control of the integrating platform or user. Polyscout supports both locally managed wallets and user-hosted remote signing services. When remote signing is used, private keys never leave the signer service. Polyscout only requests signatures for explicitly approved payloads and never stores private keys.