Username Checker: 13 Verified Developer & Creator Platforms

🏆 Part of The Mine Works' 149-actor portfolio · 40,000+ runs · 200,000+ results delivered across our full distribution stack · 99.9%+ success rate

💰 $1.00 / 1,000 results.

⚡ Every platform here was verified live. A handle is not judged by guesswork, it is tested against a real known account and a nonsense one, and platforms that could not tell the two apart were dropped. 💸 Pay per username checked, not per platform. A run with no usernames is never billed.

Check whether a username exists on GitHub, YouTube, Behance, Flickr, SoundCloud, HackerOne, Bitbucket, Dev.to, Goodreads, Blogspot, Itch.io, Gumroad and Buy Me a Coffee, all in one call. No login, no browser session, no API key.

Why 13 platforms, not hundreds

Most username checkers on the market advertise coverage across hundreds of sites. Before writing a single line of this actor, every candidate platform was tested live: a known-real username and a random nonsense username were both fetched, and the two responses were compared. Of 51 platforms tested this way, 38 were rejected, for three different reasons:

• Some sites blocked the request outright (a 403, or no response at all): Reddit, X/Twitter, Quora, GitLab, Medium, npm and others render nothing to a plain HTTP fetch without a real browser session.
• Some sites returned the identical response for both usernames: Instagram, Twitch, Pinterest, Replit and several more serve a generic client-side shell page regardless of whether the account exists, because the actual profile data loads via JavaScript after the page arrives. A checker built against these would report every username as "found" on every one of them, silently and confidently wrong.
• One site, Houzz, looked distinguishable in initial testing but proved non-deterministic: the identical fake username returned "not found" on one request and "found" on another request minutes later. That is not a logic bug to fix, it is the site's own infrastructure being inconsistent, so it was removed rather than shipped.

The 13 platforms in this actor are the ones that gave a genuinely different, verifiable answer for a real account versus a fake one. That is a smaller number than a "460 platforms" claim, and it is also true. A checker whose site definitions nobody re-verifies degrades silently as those sites change their front ends; this one only claims what was actually confirmed working.

Input

• usernames (required): one or more usernames to check, without the @.
• platforms: optionally restrict the check to specific platforms from the 13 supported. Leave empty to check all of them.

Example output

{
 "username": "torvalds",
 "checked_at": "2026-08-30T00:00:00.000Z",
 "platforms_checked": 13,
 "platforms_found": 3,
 "results": [
 { "platform": "github", "category": "developer", "exists": true, "http_status": 200, "profile_url": "https://github.com/torvalds" },
 { "platform": "devto", "category": "developer", "exists": false, "http_status": 404, "profile_url": null },
 { "platform": "youtube", "category": "creator", "exists": true, "http_status": 200, "profile_url": "https://www.youtube.com/@torvalds" }
 ]
}

Who this is for

Checking whether your own handle is available or already taken across the platforms you actually care about before you commit to a brand name. Verifying that a candidate, contributor, or business contact's claimed usernames genuinely exist, as a lightweight identity check. OSINT and research workflows that need a fast, structured existence check rather than opening fourteen tabs by hand.

Frequently asked questions

Why isn't Instagram or Twitter/X included? Both were tested and rejected. Instagram returns the same generic page for a real and a fake username without a browser rendering the page, and Twitter/X blocks a plain HTTP request outright. Including them would mean guessing, not checking, and guessing isn't what this actor is for.

What does exists: null mean? The platform returned something other than its two verified signals (for example, a rate limit), so the result is genuinely unknown rather than assumed either way. This is rare, and the run log records it.

Can more platforms be added? Yes, but only after the same live verification: a real account must resolve differently from a nonexistent one. A platform whose front end changes to a JavaScript-only shell would be re-tested and could be removed rather than left silently wrong.

What counts as a result I'm charged for? Each username checked, regardless of how many of the 13 platforms it was found on. A run given no usernames is never charged.

Why not just check by hand? One request per platform, against a set of platforms that were each verified beforehand with a real handle and a nonsense one. A site that returns a generic 200 for any URL never makes it in, so it never shows up as a false positive. That verification step is the part manual checking skips.

Does it use each platform's API? No. Plain HTTP fetches. No login, no API keys, no per-platform rate-limit registration.

Pricing

Event	Price	You pay when
Username checked	$0.001	A username is checked across the platforms you requested

$1.00 per 1,000 checks, flat across every Apify plan. One username checked against all 13 platforms is one charge, not thirteen. There is no per-run start fee, and a run with no usernames is never charged.

Run it on a schedule

Most people run this once: clearing a brand name before launch, or verifying a handle someone says is theirs. If you want it recurring, for example watching a handle you would take if it were released, the setup is the same as any Apify actor.

1. Run it once with the input you want repeated, then click Save as a task so that exact input is attached to every future run.
2. In the Apify Console go to Schedules and create a new one, either a preset (hourly / daily / weekly) or a cron expression.
3. Save. It then runs unattended, billed the same pay-per-result way. Nothing is charged for the schedule existing.

Use from Claude, ChatGPT & any MCP agent

Hosted MCP endpoint, no install, OAuth on first connect:

https://mcp.apify.com/?tools=themineworks/username-checker

Claude Desktop / Cursor config (token auth):

{
 "mcpServers": {
 "username-checker": {
 "url": "https://mcp.apify.com/?tools=themineworks/username-checker",
 "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
 }
 }
}

Ask your agent: "Check whether the handle acme-labs is taken on the developer and creator platforms you can verify."

Part of the outbound prospecting toolkit

Clear a brand handle here, then resolve the company's official domain and its LinkedIn company page in the same pipeline.

Keywords: username checker, username availability checker, check handle availability, GitHub username checker, brand name clearance, username squatting check, social handle verification