Docs · Guide
Set up your bot
About ten minutes. You create a Discord application, give Anchor three values from it, and paste two values from Anchor back. The dashboard checks every step with Discord as you go.
Why your own bot
When a member verifies, they authorise one specific application to add them to servers. Discord only lets that same application add them later, so the application has to be yours.
It is also what keeps your members safe. A public bot that adds members back for thousands of servers is one target: when Discord bans it, because one of those servers misused it, every server using it loses its members at once. Your own private bot answers only for your servers, so nobody else's ban can take it down. That's why Anchor asks for ten minutes in the Developer Portal instead of offering one shared bot.
1. Create the application
- Open the Discord Developer Portal and press New Application.
- Name it after your server. Members see this name on Discord's authorisation screen, so “Pixelhaven” reads better than “my-bot-2”.
- Add an icon under General Information if you like; it shows there too.
2. Copy the bot token
- Open Bot and press Reset Token. Copy it now: Discord shows it once.
- Turn off Public Bot, so only you can add it to a server.
- Leave Requires OAuth2 Code Grant off, and leave every privileged intent off. Anchor needs none of them.
3. Copy the Client ID and secret
- Open OAuth2. Copy the Client ID (a long number).
- Press Reset Secret and copy the Client Secret.
4. Connect it in Anchor
In the dashboard, open Bot and paste the three values. Anchor checks them with Discord and stores them only if they work, encrypted under a key that is never kept in the database. The token and secret are never shown back to you, so keep your own copy somewhere safe or reset them when needed.
What happens to the token
- Stored encrypted, never shown again. The token and secret are encrypted before they are saved, under a key that is never kept in the database. Anchor decrypts them only to talk to Discord, and nobody can read them back, you included.
- Revoke it any time. In the Discord Developer Portal, open your application → Bot → Reset Token. The old token stops working at once; paste the new one under Bot in Anchor to carry on.
- If you stop using Anchor. Disconnect the bot (after removing its servers) and the token and secret are deleted at once. A removed server's members and backups are deleted 7 days later. Delete your account and everything stops at once; the token, servers, members, backups and logs are deleted 7 days later.
5. Add the redirect
Still under OAuth2, find Redirects, press Add Redirect and paste:
https://anchor.cartiqolabs.com/api/verify/callback
Save. This is where members come back to after approving on Discord.
6. The interactions endpoint (Anchor sets it)
When you connect the bot in step 4, Anchor sets your application's Interactions Endpoint URL for you, using the bot's own token, as long as it's empty: one you set for something else is left alone. The Bot page then shows Interactions endpoint is set in green, and there's nothing to do here.
Only if that check stays red, set it by hand: under General Information, paste this into Interactions Endpoint URL, with your own Client ID at the end, and save:
https://anchor.cartiqolabs.com/api/interactions/<your client ID>
Discord tests the URL the moment you save, which is why the bot has to be connected in Anchor first. The Bot page shows the exact URL with a copy button.
7. Invite the bot
Back on Anchor's Bot page, press Add to a server. The link asks for Create Invite, Manage Roles, Manage Channels, View Channels, Send Messages and Embed Links. It never asks for Administrator.
Then press Run checks again. When every step is green, the bot is ready.
If a check fails
- Bot token works fails: the token was reset after you copied it. Reset it again and paste the new one under Replace credentials.
- Token belongs to this application fails: the token and Client ID come from two different applications.
- Interactions endpoint is set fails: Discord could not reach the URL or it has a typo. Copy it from the dashboard rather than typing it.