Aero / Get a key
Keys come from Discord. Nothing else.
One button, inside the server. No waiting-room timer, no paid tier, and no key that any third party can hand you. The flow below is what the bot implements, including the exact failure messages.
The flow
- Join the Discord server. Neither this site nor a DM can issue a key.A site or message offering an instant Aero key is a clone.
- Press Get A Key on the panel.The server's key panel has a Get A Key button. It mints one bound to your account, and you can hold one live key at a time — the reply says when the next claim unlocks.
- Or redeem a code staff gave you:
/key redeem <AERO-XXXX-XXXX-XXXX>Staff run /key generate or /key custom in the Discord server. The reply is ephemeral — it shows the expiry, or the reason it failed. - Check before you claim it is broken.View Key on the panel lists the keys you hold and when each one expires.
A key is bound to the first account that redeems it; a second account gets 'already redeemed'.
Key anatomy
AERO-XXXX-XXXX-XXXX — three random segments from a small alphabet:
ABCDEFGHJKLMNPQRSTUVWXYZ23456789
No I, no O, no 0, no 1, so a key read out loud still types correctly. Input is uppercased before lookup, so lowercase pastes work.
| Piece | Value |
|---|---|
| Prefix | AERO- |
| Segments | 3 |
| Characters per segment | 4 |
| Custom keys | Must still start with AERO-, e.g. AERO-VIP-YOUTUBER |
What each reply means
| Reply you see | What happened | What to do |
|---|---|---|
| Invalid key | No such key in this server. Typos are the usual cause. | Re-type it exactly. If staff issued it, ask them to confirm with /key info — that command is staff-only. |
| Key revoked | Staff killed it with /key revoke. | Open a ticket if you believe that was a mistake. |
| Key expired | Past its expiry timestamp. | Ask in a ticket: staff can issue a new key or move this one's expiry with /key extend. |
| Already redeemed (you) | Your account already spent it. | Nothing to do; your copy is the one that works. |
| Already redeemed (someone else) | The key was shared or leaked and got spent first. | Ticket it with the timestamp of when you received it. |
Durations
Set by the issuer, never by you: 1h · 12h · 24h · 7d · 30d · lifetime. Anything else — "2w", "90 days" — is rejected as an invalid duration. The redeem reply prints the expiry as a Discord timestamp.
No promise about supply. Nobody has to issue a key, and nothing here predicts when the next one lands.
When it goes wrong
/ticket opens a support ticket with the bot's ticket system. The channel is private and closing it writes a transcript. Include the key, the exact reply text, and roughly when you got the key.
No public invite link. Keys are issued inside the Discord server; ask a current member for an invite.