Discord Username Checker — Server or User

What does Discord Username Checker do?

Discord Username Checker tells you whether a Discord username or server vanity invite is available or already taken. Paste a list of handles / codes, pick one entityType per run (default user), and download clean JSON / CSV / Excel from the dataset.

Built for bulk brand / vanity research (up to 100,000 items per run). Large lists are auto-split into ~3,000-item child runs on Apify, with auto-heal under rate limits. Lightweight HTTP - 256 MB, no browser.

This Actor is not affiliated with Discord. Vanity checks use the public invite API (solid). Username checks use an unauthenticated attempt endpoint (best-effort - Discord may change it).

Key features

• Bulk checks - up to 100,000 items per run (invalid / duplicate inputs filtered before work starts)
• One mode per run - user or vanity (never both in one paid call)
• Auto-sharding - runs above ~3,000 split into child runs; one parent dataset
• Auto-heal - on blocks / timeouts: backoff and lower concurrency
• Vanity invites - discord.gg/{code} via invite API (404 = free)
• Usernames - best-effort pomelo username availability
• Success-only billing - only conclusive checks charge PPE result
• Export anywhere - JSON, CSV, Excel, HTML from the Apify dataset

Why Clovys

Clovys is a nonprofit organization driven by a single mission: to make the internet safer, faster, more reliable, and universally accessible.

We believe that data should not be locked behind exorbitant paywalls or complex technical barriers. By building lightweight, highly optimized Apify Actors, we help developers, researchers, and organizations access the information they need to innovate without friction.

As a nonprofit initiative, we do not optimize for margins. Our pricing is kept as low as possible and is strictly calculated to cover the raw infrastructure costs of data extraction - such as Apify compute units and proxy bandwidth.

For Discord specifically, Clovys separates vanity (stable invite API) from user (best-effort) so you only pay for the mode you need.

Use cases

• Community branding - reserve vanity invite codes (discord.gg/-)
• Creator / brand handles - screen Discord usernames before launch
• Agency workflows - bulk-check client name ideas
• Multi-platform suites - pair with other Clovys username checkers

How to use

1. Open Discord Username Checker in Apify Console
2. Paste usernames or vanity codes
3. Leave entityType as user, or switch to vanity for invite codes
4. Click Start
5. Download results from the Dataset tab

Input

Field	Type	Default	Description
usernames	string[]	-	Usernames or vanity codes (required, up to 100,000)
entityType	string	user	user or vanity - single value only
maxConcurrency	integer	3	Parallel checks (1-10)
maxRetries	integer	2	Retries on network / ambiguous responses
requestDelayMs	integer	200	Pause after each check (0 = off)

Output example

You can download the dataset in JSON, HTML, CSV, or Excel.

{
 "platform": "discord",
 "entityType": "vanity",
 "username": "discord",
 "available": false,
 "displayName": null,
 "profileUrl": "https://discord.gg/discord",
 "method": "discord_invite_api",
 "checkedAt": "2026-09-26T01:00:00.000Z",
 "error": null
}

Taken and available rows are successful results. Ambiguous / failed rows keep available: null and error set - they are not billed.

Data fields

Field	Description
platform	Always discord
entityType	user or vanity
username	Normalized handle / vanity code
available	true = free, false = taken, null = inconclusive
displayName	Guild name when vanity is taken (if exposed)
profileUrl	Invite or user URL
method	discord_invite_api or discord_username_attempt
checkedAt	ISO timestamp
error	Error message if the check failed

Pricing

Pay-per-event pricing (platform usage is billed separately by Apify):

Event	When charged	Price
result	Each conclusive check (available true or false)	$0.004 ($4 / 1,000)
Actor Start	Once when the run starts (scaled by memory GB)	$0.001

Example: 1,000 conclusive checks ~ $4.00 in PPE result (+ Actor Start + Apify platform usage).

Only conclusive results are charged as result. Failed / ambiguous rows are free on the PPE event. Checking both user and vanity means two runs.

Recommended settings

Goal	Settings
Production / vanity	256 MB, entityType: vanity, concurrency 3-5
Usernames	entityType: user, concurrency 2-3 (best-effort endpoint)
Huge lists	up to 100,000 items - auto-shard handles the rest

FAQ

How many usernames per run? Up to 100,000. Lists above ~3,000 are auto-split into child runs; invalid / duplicate inputs are dropped before sharding.

Is "taken" billed? Yes. Both available: false (taken) and available: true (free) are conclusive result events. Only error / inconclusive rows are free.

Can I check users and vanity in one run? No. entityType is a single value. Run once per mode (separate billing).

Which mode is more reliable? Vanity (invite API) is the solid path. User is best-effort and may return more ambiguous results if Discord changes the endpoint.

Do I need proxies? Usually no. Add proxy only if you hit sustained rate limits.

Is this official Discord data? No. This Actor is independent and unaffiliated.

Support

Questions, bugs, or feature requests: use the Actor Issues tab on Apify, or contact Clovys through the Store profile.