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 or vanity codes, pick one mode per run (user or vanity), and download clean JSON / CSV / Excel.

Built for bulk brand and vanity research — up to 100,000 items per run. Large lists are handled automatically so you get one dataset without babysitting the job. Lightweight by default (256 MB).

This Actor is not affiliated with Discord.

Why use it

• Know before you launch — screen handles and vanity codes before branding a community
• Bulk without friction — paste a long list; the Actor scales the work for you
• Clear yes / no — each row is available, taken, or inconclusive
• Pay for answers — only conclusive checks are billed; failed / ambiguous rows stay free
• Export anywhere — JSON, CSV, Excel, HTML from the Apify dataset

Use cases

• Reserve vanity invite codes (discord.gg/...) for communities
• Screen Discord usernames before a product or creator launch
• Bulk-check client name ideas for agencies
• Pair with other Clovys username checkers for multi-platform naming

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 — one mode per run
userCheckMethod	string	suggest	Check strategy for user mode (keep default unless you know you need another)
maxConcurrency	integer	5	Parallelism (1–10)
maxRetries	integer	3	Retries on temporary failures
requestDelayMs	integer	250	Pause between checks
proxyConfiguration	object	residential	Proxy settings (residential recommended for user mode)

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",
  "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	Display name when available
profileUrl	Invite or user URL
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. Checking both user and vanity means two runs.

Recommended settings

Goal	Settings
Production	256 MB, defaults, concurrency 3–5
Usernames	entityType: user, residential proxy
Vanity invites	entityType: vanity
Huge lists	up to 100,000 items — leave defaults

FAQ

How many usernames per run? Up to 100,000. Invalid and duplicate inputs are filtered before work starts.

Is "taken" billed? Yes. Both taken and available are conclusive. Only inconclusive / error rows are free.

Can I check users and vanity in one run? No. Pick one entityType per run.

Do I need proxies? Residential is recommended for user mode. Vanity often works with lighter settings.

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.