Key pools per serverGroup keys by game or drop. Each pool has its own claim limit, key type, required roles, and moderator roles. Keep a pool private for grant-only distribution, or open it up for self-serve.
Hand out game keys in Discord, without the spreadsheet
KeyBot stores your keys in per-server pools and gives them out on request. Set who can claim, how many, and when. It handles the rest, from bulk import to knowing exactly who got what.
- Servers
- 2,600+
- Keys delivered
- 78,000+
- Active pools
- 1,400+
How it works
- Add KeyBotInvite it to your server. It only needs permission to send messages, embed links, and attach files.
- Create a pool and import keysName the pool, pick Steam or custom keys, set how many each member may claim, then upload your key file.
- Members claimThey run /claim and KeyBot sends the key privately, checking roles, bans, and limits first.
What you get
Bulk importUpload a .txt, .csv, or .json file and KeyBot loads the whole batch, skipping any key already in that pool. Import tens of thousands at once without touching a spreadsheet.
Role gating and bansRequire one or more roles before a member can claim. Ban individuals from a single pool or from every pool in the server when someone abuses a drop.
Keys reach the right person, onceClaims are issued atomically, so two people racing the same command can never be handed the same key. Per-user limits are enforced server side.
Stock warningsPoint KeyBot at a channel and it tells you when a pool drops below ten percent, and again when it runs dry, so a drop never quietly stops working.
Audit and lookupFind who claimed a specific key, or every key a member has claimed, with timestamps. Export the unclaimed remainder of any pool at any time.
Premium, when you need moreAnti-alt rules, scheduled drops, whitelists, custom key messages, analytics and webhooks, plus no caps, for $3 per 30 days per server. No subscription, nothing deleted when it ends.
Hydra One Every Team Hydra bot, premium, on one server. Overbuilt on purpose. Get Hydra One