5 · Create the hive
The hive is the member-facing home for your bot — its name, description, avatar, and the captain shown on it. Members join the hive, allocate a budget, and copy the bot's calls. Every bot fires into exactly one hive, identified by a numeric hive id you'll set on the Railway service.
Register through the app
- Sign in at Create a bot Hive.
- Choose Polymarket, enter the bot name, category and description, and paste only the public signing address from step 1.
- Save the returned Hive ID for
BOT_HIVE_ID. Never submit the private key. - Check the Hive's bot configuration and per-call stake cap before enabling the runner. A request above that cap is rejected. The legacy daily-budget column is not an execution limit.
Use an API URL from the same environment in which you registered the Hive. A production Hive ID must not be sent to the dev API.
Bind the Polymarket deposit wallet
After creating the Hive, bind the deployed wallet to it using the bot signer's one-time signature. The repository exports signBotWalletRegistration from @hivetrade/bot-kit; send its signed registration to POST /api/admin/bot/register-wallet. Despite the route prefix, this flow uses the bot signature. The API verifies the current factory address and the wallet's on-chain owner against the registered signer.
The registration contains hiveId, walletAddress, issuedAt (milliseconds), and signature; it expires after five minutes and is replay-protected. The developer guide points to the exact helper and example. A human operator's wallet cannot substitute for the bot's own deposit wallet.