# Twitter / X Username Checker (`maged120/twitter-username-checker`) Actor

Checks whether Twitter / X usernames (handles) are available or already taken.

- **URL**: https://apify.com/maged120/twitter-username-checker.md
- **Developed by:** [Maged](https://apify.com/maged120) (community)
- **Categories:** Automation, Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Twitter / X Username Checker

**Bulk-check whether Twitter / X usernames (handles) are available or already taken.** Feed in a list of handles and get back a clean, structured result for each one — available or not. Duplicates and invalid handles are filtered out automatically, so you never waste a check.

### What does Twitter / X Username Checker do?

This Actor takes a list of [X (Twitter)](https://x.com) handles and tells you, for each one, whether it can still be registered. It's built for speed and runs entirely on the [Apify platform](https://apify.com), so you get API access, scheduling, integrations, proxy rotation, and run monitoring out of the box — no browser or local setup required.

### Why use Twitter / X Username Checker?

- **Brand protection** — confirm your brand or product handle is still free before someone else grabs it.
- **Handle hunting** — find short, clean, or on-brand handles that are still available.
- **Bulk research** — check hundreds of handles in one run instead of typing them one by one.
- **Automation** — schedule recurring checks and wire the results into your own tools via the API.

### How to use Twitter / X Username Checker

1. Open the Actor and go to the **Input** tab.
2. Paste your list of handles (one per line). The `@` prefix is optional and case doesn't matter.
3. (Optional) Adjust the proxy settings.
4. Click **Start** and wait for the run to finish.
5. Download your results from the **Output** tab.

### Input

| Field | Description |
| --- | --- |
| **Usernames to Check** | The list of handles to verify (up to **1000** per run). `@` is optional, case is ignored, and duplicates are removed before checking. Unique handles beyond the first 1000 are skipped. |
| **Proxy Configuration** | Proxy settings. Residential proxies are recommended for large lists. |

Example input:

```json
{
    "usernames": ["jack", "my_cool_unclaimed_handle", "@SomeBrand"],
    "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

### Output

Each handle becomes one row in the dataset. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

```json
[
    {
        "username": "jack",
        "available": false,
        "error": null
    },
    {
        "username": "my_cool_unclaimed_handle",
        "available": true,
        "error": null
    }
]
```

#### Data table

| Field | Type | Description |
| --- | --- | --- |
| `username` | text | The normalized handle that was checked. |
| `available` | boolean | `true` if the handle can be registered, `false` if taken, `null` if it couldn't be checked. |
| `error` | text | Populated only for invalid handles or handles that couldn't be checked. |

### How much does it cost?

Cost scales with the size of your list — you're billed per result, and each handle produces exactly one result. Duplicate and invalid handles are filtered before any checks run, so you only pay for real, unique handles. A run of a few hundred handles typically costs a small fraction of a compute unit.

### Tips

- For large lists, keep the default **residential proxy** setting on to avoid rate limiting.
- If you see rows with an `error`, re-run just those handles.
- Valid X handles are 1-15 characters, letters, numbers, and underscores only — anything else is flagged as invalid without spending a check.

### FAQ, disclaimers, and support

**Is this legal?** The Actor only checks public handle availability — the same information anyone sees when viewing a profile or signing up. It does not access private data or log into any account. You are responsible for complying with X's Terms of Service and applicable laws.

**Why is a handle marked unavailable when no profile is visible?** X reserves many handles (suspended, deactivated, or held) even when no public profile shows. Availability reflects whether the handle can be registered, not whether a profile currently exists.

Found a bug or need a custom version? Open an issue on the Actor's **Issues** tab and we'll take a look.

# Actor input Schema

## `usernames` (type: `array`):

Twitter / X handles to check (up to 1000 per run). The @ prefix is optional and case is ignored. Duplicates are removed automatically before checking, and any usernames beyond the first 1000 unique ones are skipped.

## `proxyConfiguration` (type: `object`):

Proxy settings to avoid rate limiting. Residential proxies are recommended for large lists.

## Actor input object example

```json
{
  "usernames": [
    "jack",
    "elonmusk",
    "my_cool_unclaimed_handle"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "usernames": [
        "jack",
        "elonmusk",
        "my_cool_unclaimed_handle"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("maged120/twitter-username-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "usernames": [
        "jack",
        "elonmusk",
        "my_cool_unclaimed_handle",
    ],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("maged120/twitter-username-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "usernames": [
    "jack",
    "elonmusk",
    "my_cool_unclaimed_handle"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call maged120/twitter-username-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maged120/twitter-username-checker"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/lKSHEdIgjAcKfODaa/builds/EhnHgoCmN4d5dxqaH/openapi.json