PredictionToolkit logoPredictionToolkit
Language: English
Search tools
← CLI tools

SDK

Polymarket CLI: move from public queries to explicit account commands

Polymarket CLI is an official Rust command-line client for market discovery, book queries and account operations. Public browsing works without a wallet, while order management and on-chain actions use separately configured account access.

3.5/ 5Editorial ratingEditorial assessment
Read the official Polymarket CLI repositorygithub.com
Available on
CLI

Screenshots and interface

Product preview1 / 2

Repository introduction to installation and public queries.

What is Polymarket CLI?

The same interface supports quick table views and machine-readable JSON for scripts. Discovery covers markets, events, tags and series; public queries also include comments, profiles and sports metadata. Price queries distinguish bid/ask-side prices, midpoint, spread and the last trade.

Account commands cover orders, cancellation and supported conditional-token actions. Keep the input semantics explicit: market IDs, condition IDs and outcome-token IDs serve different commands, and limit-order size counts outcome shares while a market-buy amount specifies spending. The repository describes early experimental software, and its older proxy, EOA and Safe examples require a check against the installed version’s account support.

Who it is for

  • Developers scripting market discovery and price reads.
  • Terminal users inspecting a contract quickly.
  • Operators adding explicit commands to account workflows.

Features and coverage

  • Discovery

    List and search markets, events, tags and series.

  • Public context

    Read comments, profiles and sports metadata.

  • Book and price reads

    Retrieve books, side-specific prices, midpoint, spread and last trade.

  • Batch queries

    Read several outcome tokens with a single command.

  • Script output

    Use JSON output together with process exit status.

  • Order controls

    Create, inspect and cancel orders for the configured account.

  • On-chain actions

    Use supported approval, split, merge and redemption commands, which submit transactions.

Workflows with Polymarket CLI

Write a research script

Search markets, save outcome-token IDs and request books as JSON. Parse the error object and check process exit status explicitly.

Inspect an order candidate

Read the exact contract, tick size, fee rate and relevant ask or bid before constructing an order command.

Operate an account

Inspect the configured wallet identity and signature type, then use order and cancellation commands limited to the intended scope.

Pricing and total cost

No subscription is listed for the public CLI. Venue fees and applicable on-chain transaction costs remain separate.

Getting started

Before you start: Limit-order size is an outcome-share count; a market-buy amount is a spend amount.

  1. Install using the official repository’s supported package or build route.
  2. Begin with a small public market listing.
  3. Use -o json for scripting.
  4. Resolve the correct outcome token before book or order commands.
  5. Configure wallet identity only when account actions are needed.
  6. Compare the installed release with current official wallet and client conventions.

Market IDs, condition IDs and outcome-token IDs are different inputs for different commands.

Useful links

    What to check

    • Limit-order size is an outcome-share count; a market-buy amount is a spend amount.
    • README wallet examples use older proxy, EOA and Safe conventions; verify the installed version’s support for your account type.
    • JSON errors are written to stdout with an exit status other than 0.
    • Approval and conditional-token commands submit transactions rather than merely reading data.

    A closer look

    Ratings & reviews

    Editorial rating
    3.5/ 5
    0 user reviews
    PredictionToolkit editorial

    Our take on Polymarket CLI

    Table and JSON output make public discovery and scripted reads convenient. Older wallet examples and the difference between outcome-share size and spend amount need checking before enabling account commands.

    Based on documented features, setup and access terms. How we rate

    User reviews 0

    The main score switches to user ratings after 5 published reviews.

    Be the first to share your experience

    A specific example helps the next person choose the right tool.

    Related tools

    Browse category
    Official Polymarket CLOB price and book documentation
    Polymarket CLOB API
    Data API4.0Editorial

    Read outcome prices and depth, then handle authenticated orders through a separate signing boundary.

    • Access API

    The underlying book-data and execution interface.

    Official Polymarket Python SDK installation and quickstart
    Polymarket Python SDK
    SDK4.0Editorial

    Typed sync and async clients for scripts, notebooks, account workflows and real-time subscriptions.

    • Language Python

    Use a Python library within a larger application.

    Polygate research and account tools with connection choices
    Polygate
    SDK3.5Editorial

    Run public market research locally or connect a supported web client through a temporary authenticated tunnel.

    • Language Python
    • Access CLI · MCP

    Expose similar operations through MCP.

    Frequently asked questions about Polymarket CLI

    Can I browse without a wallet?

    Yes. Public market, price and book queries work without credentials.

    How should a script detect failure?

    Read the JSON error output on stdout and check for an exit code other than 0.

    Is a side price the midpoint?

    No. A side-specific price refers to a bid or ask; midpoint is a separate query.

    Which cancellation scopes are available?

    The documented commands support individual, grouped, market-scoped and all-order cancellation.