Build a custom bot
A bot is an automated Captain attached to one Hive and one venue. Its public signing address is registered in the app; the private signing key stays on the computer or service you control.
Choose your starting point
- The public bot repository contains the historical Polymarket starter and strategy material. It is not a current drop-in runner: the September 15 review found legacy URLs and a signal submission missing the required intent/fill flow. Do not enable it unchanged.
- The Polymarket runner guide and Kalshi runner guide describe the built-in runners for contributors with HiveTrade repository access.
- A custom strategy needs implementation and testing. Selecting a built-in
BOT_NAMEdoes not load arbitrary strategy code.
Registration and execution
Register at Create a bot Hive, select the venue, supply the public signer and save the Hive ID. Configure the matching API environment and a per-call cap appropriate to your strategy.
Polymarket self-managed bots submit a signed intent to POST /api/bot/signal with intent: true, then execute their own Captain leg after acceptance and report the actual result to POST /api/bot/signal/:id/fill. A supported fire-first submission includes its real fillResult instead. Never invent a fill or report a no-fill merely to finish a pending request.
The first-party Kalshi path sends a signed v2 intent with execution: "hivetrade-v1", an exact ticker, contract count and price limit. HiveTrade owns execution through the connected operator credential. That runner must not place a local order or post a Polymarket-style fill report.
There is currently no verified public, drop-in Kalshi starter. The built-in runners require repository access; a custom public integration requires implementing and validating the current contract.
There is currently no verified public, drop-in Kalshi starter. The built-in runners require repository access; a custom public integration requires implementing and validating the current contract.
The exact byte-level signing contract is in the repository's developer guide and packages/bot-kit/src/botSignal.ts (repository access required). Use its exported message builders; prose on this page is not a substitute for the signed wire format. Keep timestamps, nonces and truthful venue receipts intact.
Start with live trading disabled, verify configuration, and enable real orders only deliberately. Monitor both the runner and venue receipts continuously.