Prediction Market Trading Bots & Terminals

What this category is for

Everything else in this catalogue is something you read. This is the part you run. A terminal, a front end or a bot is a product that holds a credential — an exchange API key, or on the on-chain venues a wallet private key — and sends orders with it. That changes which questions matter. A data API is judged on coverage and latency; a trading client is judged on what it does with the key while it runs, and on what it takes per fill.

A package you import into your own code to do the same thing — a venue's official SDK, CCXT, PMXT — is a different purchase with different questions, and it has its own section: SDKs and client libraries.

Two facts decide most choices here, and neither is a feature. One is where your key goes. The other is the one nobody expects: some of these take a cut.

Open source is not the same as safe to hand a key

This is the sentence this category exists to print. An MIT licence is permission to read the code, not evidence that anyone did. A bot you run yourself holds your credential inside the same process as every dependency it pulls in.

Concretely, before you point a client at a funded account:

• Know which credential it wants. An exchange API key that can be scoped to trading is a different level of exposure from a wallet private key that can move funds. On the on-chain venues, signing an order and moving the collateral are both done with the same key.
• Know what it uploads. A client that signs locally and posts a signed payload is doing the right thing; a client that asks for a key so it can call a service you do not control is not.
• Check the dependency list, not just the repository. Supply-chain risk lands in the same process as the key.
• Separate the read path from the trade path. The venues answer price and order-book reads without a key. Anything you are only reading does not need one at all.

Nothing in this category has been run against a funded account by this site, so every card here is hands_on: false. The licences, the fee schedules and the key arrangements are read out of the repositories and the vendors' own pages; the behaviour under load is not something we are claiming.

Some of them charge you, and the venue's fee is not the whole fee

A library takes nothing. You install it, it signs an order, and what the fill costs is whatever the venue charges — the curve on its card, and nothing else.

It stops being true the moment the product has a front end. A consumer app that routes your order to somebody else's order book has an obvious place to take a margin, and it is inside the fill, where you will not see it as a line item.

Polycool is the explicit version: a percentage of every successful trade, on a ladder that starts at 1.00% and falls to 0.50% on lifetime volume, with a floor of three cents per execution — which makes a small copy proportionally far more expensive than the headline rate. That is charged on top of whatever Polymarket takes, and the card says so in its first line.

Synthesis is the other version, and the more common one. For a year its site had no pricing page, no fee page, and terms that ran to thousands of words without mentioning a charge to the user, so its card left the fee fields empty rather than setting them to zero: empty renders as "unknown", and zero would have claimed we established that nothing is taken. A docs site read on 9 October 2026 now states a 0.50% fee on copytrade orders, which the card carries as 0.25 cents a share at 50 cents, and still says nothing about an order placed by hand. Treat an unpublished fee as unstated, not as free.

So the question to ask a front end is not what it costs to install. It is what it takes per fill, where that is written down, and what happens to the number as you trade more.

What is in here so far

Terminals that put one or more venues in a single screen, Telegram and web bots that copy a wallet the reader chooses or re-price the reader's own orders, and a few open-source projects you run on your own machine. Three wallet trackers that can also place an order are listed here as secondary members, because placing it is the second job each of them is hired for.

Copying a wallet is the job most of the bots here are bought for, and it has a page of its own: the copy-trading collection is every card on the site whose product itself mirrors a wallet you chose into your own account, across this category and the wallet trackers, and how to copy a Polymarket wallet's trades is the task walked through to the places it breaks. The line the collection draws is the one this whole catalogue draws: you pick the wallet. A product whose deliverable is a wallet it picked for you, or a signal it trades on your behalf, is not here.

What is deliberately absent is larger than what is here. The community lists carry dozens of Polymarket bots, and most of them fail the entry test in the same three ways: no licence file, no release and no commit inside a year, or no answer to the question of what the thing does with the key you hand it. A hosted service that decides which contract to buy and sells you the answer is outside this catalogue altogether — that boundary is a product one, not a technical one, and it does not move because the product is popular.

So the listing grows one checked repository at a time, and a name we could not verify is a name that is not here.