Discord Username Availability Checker

This actor tells you whether a batch of Discord usernames is available, taken, or invalid, so you can decide which handle to claim or skip — without logging in, captchas, or any user token. Call it with a list of candidate handles and it returns a clean status row per handle straight from Discord's own signup availability API, with an available flag you can feed directly into a registration or naming decision.

It is designed for anyone who needs to verify Discord handle availability at scale: community organizers reserving a giveaway name, brands confirming a handle that matches across platforms, content creators keeping a consistent name, or developers who want a tokenless availability check for a tool or workflow.

Why it works as a focused standalone workflow

This actor is designed as a focused standalone workflow: you run one batch, read the dataset rows, and act on them. It produces a complete answer in a single run and needs no other tooling, chaining, or external service to be useful.

Output: per-handle results

For each input handle, the actor writes one dataset row with a stable status. The available boolean is the key decision field; status is the human-readable classification.

Field	Meaning
status	One of available, taken, invalid, rateLimited, or unknown.
available	true when the handle is free to claim.
taken	true when the handle is already in use.
reason	Context for invalid results (for example, length or allowed characters).
checkedAt	ISO timestamp of when the check ran.

{
  "username": "novanex",
  "requestedUsername": "Novanex",
  "status": "available",
  "available": true,
  "taken": false,
  "checkedAt": "2026-08-17T00:00:00.000Z"
}

Quick start: input

Provide one or more username candidates. Only usernames is required.

{
  "usernames": ["novanex", "coolname_23"],
  "maxConcurrency": 8,
  "proxyCountry": ""
}

Handles are case-insensitive and are de-duplicated, so casing does not cost you extra checks.

Pricing (Pay per event)

This actor uses Pay per event (PPE) with platform usage passed through to the end user. There are two event types:

• Actor start — charged once per run to cover initialization and proxy wiring.
• Username checked — charged only for handles that received a definitive answer (available, taken, or invalid). Handles that could not be checked are not billed.

Cost scales 1:1 with definitive results, so a batch of 25 handles whose every check succeeds is 25 checked events plus the single start. The live Pricing tab on this actor is the current source of truth for exact event prices.

Run one from the API

curl -X POST \
  "https://api.apify.com/v2/acts/khadinakbar~discord-username-checker/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "usernames": ["novanex", "coolname_23"] }'

Then read the dataset for the run to collect the per-handle status rows.

Workflow: from candidate list to claim

Start with your shortlist of candidate handles. Pass them all in one usernames array, and the actor checks them concurrently. Then compare the available: true rows to pick the handle you want, and claim it in Discord's signup flow. Because results drop into the dataset as structured rows, you can export them, schedule a periodic re-check of your shortlist, or feed the available handles into your own registration script.

Using this from an AI agent or MCP tool

An agent can treat this as a tokenless availability probe. Pass the candidate handles as input, then read the run's dataset for per-handle status and available.

Invoke the actor with a shortlist, read back the dataset status rows, and use each row's available flag plus cost context to decide which handle to claim. A run that never reaches Discord returns only rateLimited or unknown statuses and leaves the claim decision open. The dataset is the unit you read back, cost is driven by definitive results, and pagination is not needed because one run covers the full batch you submit.

Best-fit guidance and scope

This actor is the right fit when you want a tokenless verdict on whether Discord handles are free, at any batch size up to 500. For best results, provide a focused shortlist you actually plan to use, keep concurrency at the default unless Discord throttling appears, and schedule repeat checks if you are monitoring a name that may become available. If a handle comes back rateLimited, wait and run it again rather than treating it as taken — throttled checks are not billed to you.

To validate claims before spending, confirm you are authorized to check the target handles and that you intend to use the result within Discord's site terms.

Builder's note

I built this because checking Discord username availability normally means opening the registration form repeatedly, one handle at a time, with no way to compare a batch. I found the unauthenticated signup endpoint returns a clean taken/available verdict with no captcha, so the whole actor stays tokenless — no login, no stored credentials, nothing to break when Discord rotates authentication. In my testing, rotating a fresh residential session per request is what keeps bulk checks from tripping the per-IP throttle, which is why the actor handles retries and low-concurrency runs gracefully. My goal was a drop-in answer for the most common question — "is this name free?" — resolved in one run with per-handle rows.

Responsible use

Use this actor only for handle availability checks you are authorized to perform and that comply with Discord's site terms and any applicable laws in your region. It performs read-only availability lookups and takes no registration action on the names it checks.