Watson - Username Finder

🕵️ Watson Username Finder – OSINT Username Search Across Social Platforms

The Watson Username Finder is a username search scraper that checks a list of usernames across a set of popular social, coding, gaming and music platforms and tells you exactly where each handle exists. Give it one handle or five hundred, and it returns a clean, flat dataset row for every username-and-site combination it tested, complete with the canonical profile URL and a simple boolean telling you whether the account was found.

Username enumeration is one of the oldest and most reliable techniques in open-source intelligence (OSINT). People reuse handles. A developer who is janedoe on GitHub is very often janedoe on Reddit, on Instagram and on Steam. This username finder automates that correlation step so that analysts, recruiters, brand-protection teams and growth marketers do not have to open twenty tabs by hand. The output is deliberately boring and machine-friendly: one row, five fields, no nesting, ready to drop into a spreadsheet, a CRM or a graph database.

---

📊 What Data Can You Extract with This Username Finder Scraper?

Every dataset item produced by the Watson Username Finder describes a single check: one username tested against one site. The fields group naturally into the following categories.

Category	Fields	What it gives you
👤 Identity	username	The account handle that was searched, echoed back on every row so results stay joinable to your input list
🌐 Platform	site	The human-readable name of the platform that was checked, for example GitHub or Reddit
🏷️ Classification	category	The vertical the platform belongs to, such as coding, social, gaming or music
🔗 Destination	url	The canonical profile URL for that username on that site, ready to open or enrich further
✅ Result	found	A boolean flag stating whether an account exists at that URL

The single most useful field here is found combined with category. Because every row carries a category label, you can aggregate a person's digital footprint by vertical in one pivot: a handle that returns found: true across three coding sites but nothing in social tells you something meaningful about who you are looking at, long before you read a single profile page.

---

🌟 Key Features of the Username Finder Scraper

Feature	Description
🔁 Batch username lookup	Pass an array of usernames in a single run; the scraper iterates every handle against every supported site and emits one row per combination
🧭 Multi-platform coverage	Checks handles on major destinations including GitHub, Reddit, Instagram, Spotify and Steam Community
🏷️ Built-in categorisation	Each result carries a category label so you can slice a footprint by coding, social, gaming or music without maintaining your own lookup table
🔗 Ready-made profile URLs	The url field is the canonical profile address, so results are immediately clickable and can be piped straight into a profile-detail scraper
✅ Explicit found flag	The found boolean removes ambiguity — you never have to infer availability from an HTTP status code or a page title
📐 Flat, joinable schema	Five scalar fields, no nested objects, no arrays — the dataset imports cleanly into Excel, Google Sheets, BigQuery or Postgres
🚀 Lightweight HTTP engine	Built on curl_cffi with browser impersonation rather than a headless browser, which keeps runs fast and resource-light
🧩 Deterministic output shape	Every row has the same five keys whether the account was found or not, so downstream parsers never break on missing fields
📤 Native Apify dataset export	Results are pushed to an Apify dataset and can be downloaded as JSON, CSV, XLSX, XML or HTML, or pulled through the API

---

🚀 Why Choose This Username Finder Scraper?

Correlation, not just availability. Many tools answer only "is this handle free?". This username finder answers a more valuable question: "where does this handle already exist, and what kind of platform is it?" The category field turns a raw list of hits into a footprint profile you can reason about.

A schema that survives contact with real pipelines. Nested JSON is where enrichment workflows go to die. Because every item is a flat record of username, site, category, url and found, you can load a run directly into a database table or a Google Sheet with no flattening step, no json_extract, and no fragile parsing.

Negative results are first-class data. Rows where found is false are still emitted. That matters more than it sounds: knowing that a handle is definitively absent from a platform is evidence, and it lets you compute coverage percentages rather than guessing why a site is missing from the output.

Built for lists, not for one-offs. The input takes an array of usernames, so checking an entire candidate shortlist, a list of suspected impersonator handles, or every variant of a brand name is a single run rather than a hundred manual searches.

---

📥 Input

The Watson Username Finder takes one required input: the list of usernames you want to search for.

{
  "usernames": [
    "elonmusk",
    "johndoe"
  ]
}

🔧 Username Finder Scraper Input Fields

Field	Type	Required	Default	Description
usernames	array	✅ Yes	["elonmusk", "johndoe"]	List of usernames to search across platforms. Entered as a string list in the Apify console, one handle per line.

💡 Input Examples

Single handle check

{
  "usernames": ["elonmusk"]
}

Brand-name variant sweep

{
  "usernames": [
    "acmecorp",
    "acme_corp",
    "acme.corp",
    "acmeofficial",
    "theacmecorp"
  ]
}

Candidate shortlist enrichment

{
  "usernames": [
    "janedoe",
    "j_doe_dev",
    "jdoe1988",
    "notjanedoe"
  ]
}

---

📤 Output

Each dataset item is a single username-to-site check. Below is a real item returned by the username finder.

{
  "username": "elonmusk",
  "site": "GitHub",
  "category": "coding",
  "url": "https://github.com/elonmusk",
  "found": true
}

🧾 Username Finder Output Fields

Field	Type	Description
username	string | null	The account handle that was searched on this site
site	string | null	The name of the platform that was checked
category	string | null	The vertical the platform belongs to, for example coding
url	string | null	Canonical profile URL for this username on this site
found	boolean | null	Whether an account exists at that profile URL

Because the scraper emits one row per site rather than one row per username, a run over ten handles across five platforms produces fifty rows. Group by username and filter on found to reconstruct each person's footprint.

---

💻 How to Use the Username Finder Scraper (Step by Step)

Step 1: Open the Username Finder Actor on Apify

Sign in to your Apify account and open the Watson Username Finder Actor page. If you have not used Apify before, create a free account first — the Actor runs on Apify's infrastructure, so there is nothing to install locally, no Python environment to configure and no proxy credentials to manage. The Actor page gives you a form-based input editor on the left and the run log, dataset and storage tabs alongside it.

Step 2: Build Your Username List

Click into the Usernames to Search field and enter the handles you want to check, one per line. The field is a string list, so you can paste a column straight out of a spreadsheet. Think carefully about variants at this stage: real people and real brands rarely use one consistent handle everywhere, so including underscore, dot and numeric variations of the same base name will materially increase your hit rate.

Step 3: Start the Run and Watch the Log

Press Start to launch the username search. The log streams progress as each handle is tested against each supported platform. Runs are quick because the scraper uses plain HTTP requests with browser impersonation rather than launching a headless browser, so there is no page rendering overhead. Larger username lists simply take proportionally longer — the work is linear in the number of handles.

Step 4: Review the Dataset

Open the Dataset tab once the run finishes. You will see a flat table with the five output columns: username, site, category, url and found. Sort by found to bring the hits to the top, or sort by username to read one person's footprint as a contiguous block. The preview table is a good place to sanity-check that your handles were spelled as you intended before you export anything.

Step 5: Filter to the Rows That Matter

Most workflows only care about rows where found is true. Apply that filter in the dataset view, or apply it at export time using the Apify API's field and filter parameters. If you are measuring handle availability instead — for a brand launch, say — invert the logic and keep the found: false rows, which tell you which platforms still have your desired name free.

Step 6: Export or Push Downstream

Download the filtered dataset as CSV or XLSX for manual analysis, or as JSON if it is feeding another system. For recurring work, set up an Apify integration so that each finished run pushes results directly to Google Sheets, Slack, or a webhook endpoint of your own. The flat schema means no transformation step is needed between the dataset and almost any destination.

Step 7: Chain into Profile Enrichment

The url field is the natural hand-off point. Feed the found URLs into a platform-specific profile scraper to pull follower counts, bios, repository lists or post history, and you have turned a username list into a full enrichment pipeline. Because site and category travel with every row, you can route each URL to the correct downstream scraper automatically.

---

🔌 API Access & Integrations

Run the username finder programmatically and get results back in the same request using the Apify API.

curl -X POST "https://api.apify.com/v2/acts/scrapers-hub~watson-username-finder/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "usernames": ["elonmusk", "johndoe"]
  }'

The same run is a few lines with the official Python client:

from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")

run = client.actor("scrapers-hub/watson-username-finder").call(
    run_input={
        "usernames": ["elonmusk", "johndoe"],
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    if item.get("found"):
        print(item["username"], "→", item["site"], item["url"])

Beyond the API, results from the username finder can be routed automatically to Zapier, Make, Google Sheets and Slack, or delivered to any endpoint you control using Apify webhooks that fire when a run succeeds.

---

💡 Best Use Cases for Username Search Data

🔍 OSINT and Digital Footprint Mapping

Investigators use username enumeration as an early pivot. Run a subject's known handle through the username finder, keep the rows where found is true, and you have a map of their presence across coding, social, gaming and music platforms in one pass. The category field lets you characterise the footprint at a glance rather than reading every profile.

🛡️ Brand Protection and Impersonation Monitoring

Check your official brand handle and its plausible misspellings on a schedule. Rows where found is true for a variant you do not own are candidate impersonation accounts, and the url field gives your legal or trust-and-safety team a direct link to file a report against.

🚀 Handle Availability for Product Launches

Before committing to a name, run every candidate through the scraper and look for the rows where found is false. A name that is free across all checked platforms is worth far more than one that is only free on your primary channel, because consistent handles are what make a brand findable.

🧑‍💻 Technical Recruitment and Candidate Research

Recruiters can take a candidate's handle from a CV and check it against coding platforms. A found: true row with category: coding and a GitHub url is an immediate signal worth following up, and it takes seconds rather than a manual search per platform.

📈 Influencer and Creator Verification

Before a partnership, confirm that a creator actually holds the handles they claim. Running their stated username through the finder and comparing site and found against their media kit is a cheap authenticity check that catches inflated or fabricated cross-platform claims.

🧩 Lead Enrichment for Sales and Growth

If your CRM already stores a handle for a contact, the scraper turns that single string into a set of profile URLs across platforms. Joining on username lets you append site and url pairs to existing records without touching your source data model.

🔐 Account Security and Exposure Reviews

Security teams performing an exposure review for executives or key staff can enumerate personal handles to find accounts that were forgotten but never deleted. Every found: true row on a consumer platform is a potential source of social-engineering material worth closing down.

---

⚙️ Tips for Better Username Search Results

• Include handle variants, not just the canonical name. Add underscore, dot, hyphen and numeric-suffix versions of each base handle. People and brands are rarely consistent, and variants are where most genuine hits come from.
• Keep negative rows during analysis. Deleting found: false rows too early destroys your ability to distinguish "not on that platform" from "that platform was never checked". Filter at the reporting stage instead.
• Batch sensibly. A single run with a long usernames array is more efficient than many small runs, but very large lists take proportionally longer, so split enormous inputs into a few scheduled runs rather than one that risks hitting your timeout.
• Normalise handles before you submit them. Strip leading @ symbols, trim whitespace and lowercase where appropriate. Clean input avoids false negatives caused by characters the platform would never accept in a URL.
• Treat a hit as a hypothesis, not proof of identity. Handle collisions are common on popular names. Always confirm with profile content before asserting that two accounts belong to the same person.
• Re-run periodically for monitoring use cases. Availability and existence both change. Schedule the Actor weekly or monthly if you are tracking impersonation or waiting for a desirable handle to be released.

---

🛠️ Troubleshooting

Why does a username I know exists come back with found: false? Platforms sometimes serve a soft error, a consent interstitial or a rate-limit page instead of the real profile, which the checker reads as absent. Re-run the handle on its own to confirm, and open the url value manually to verify before treating the negative as authoritative.

Why are some platforms missing from my results for a given username? Every run emits one row per site that was successfully checked. If a platform is absent, that site's request did not complete on this run. Re-running usually fills the gap; persistent absence for one platform across many runs points at that platform blocking automated requests.

The run finished but the dataset is empty. This almost always means the usernames input was empty or contained only blank lines. Open the run's Input tab, confirm the array actually contains handles, and check the log for a warning about missing input.

Results for very common handles look wrong. Short, generic handles are taken on nearly every platform by unrelated people, so a wall of found: true rows is expected and does not indicate one shared owner. Use longer, more distinctive handles when the goal is identity correlation rather than availability checking.

How do I stop a long-running search? Use the Abort button on the run page. Items already pushed to the dataset are retained, so you keep whatever the username finder collected before the abort.

---

❓ Frequently Asked Questions About Username Search

What does the Watson Username Finder actually do? It is a username finder scraper that takes a list of handles and checks each one against a set of supported platforms, returning a row per check with the site name, category, profile URL and a boolean saying whether the account exists.

Which platforms does the username finder check? The scraper checks handles against platforms including GitHub, Reddit, Instagram, Spotify and Steam Community, and labels each result with a category such as coding, social, gaming or music.

How many usernames can I check in one run? There is no fixed cap in the input schema — the usernames field is a plain array. Practical limits come from run time, since the work grows linearly with the number of handles multiplied by the number of platforms checked.

Do I need a login, cookies or API keys for any platform? No. The scraper only reads publicly reachable profile addresses. You supply no platform credentials, and you do not need an account on any of the sites being checked.

Does the username finder return the profile URL? Yes. Every row includes a url field containing the canonical profile address for that username on that platform, which you can open directly or feed into another scraper.

What does the category field mean? It is the vertical the platform belongs to — for example coding for GitHub. It lets you summarise a digital footprint by type of platform without maintaining your own site-to-category mapping.

Are results returned for usernames that were not found? Yes. Rows are emitted with found: false so you can distinguish a confirmed absence from a platform that was never tested. This is important for computing coverage and for availability research.

Can I use this to check if a username is available before registering it? Yes. Look for rows where found is false — those indicate no account was detected at that profile URL. Always confirm on the platform itself before building a brand around a name, since reservation rules vary.

Is this username search tool suitable for OSINT work? It is well suited to the enumeration step of an OSINT workflow. It produces the cross-platform handle map that analysts normally build by hand, but treat every hit as a lead requiring corroboration rather than proof of identity.

What output formats can I download? Apify datasets export as JSON, CSV, XLSX, XML, RSS and HTML, and the same data is available through the dataset API endpoint for programmatic access.

Can I run the username finder on a schedule? Yes. Apify's scheduler can trigger the Actor at any cron interval, which is how most brand-protection and monitoring workflows use it. Combine with a webhook to push each finished run into your own system.

Does the scraper use a headless browser? No. It uses HTTP requests with browser impersonation via curl_cffi, which is why runs are fast and lightweight compared with browser-based username checkers.

How do I integrate the results with my CRM or spreadsheet? The output is flat, so a CSV export imports directly. For automation, use the Apify integrations for Google Sheets, Zapier, Make or Slack, or configure a webhook to post the dataset to your own endpoint when a run finishes.

Why do two different people share the same username on different sites? Handles are allocated per platform and are not globally unique. Popular names are frequently claimed by unrelated individuals, which is why the scraper reports presence rather than asserting identity.

Can I check handles that contain special characters? You can submit any string, but platforms restrict which characters are valid in a handle. Handles with characters a platform does not permit will simply return found: false for that site.

---

🆘 Support & Feedback

Found a bug, or noticed a platform returning inconsistent results? Please open a ticket on the Issues tab of this Actor — issues reported there are tracked and get fixed fastest, and including the run ID helps enormously.

Need extra platforms added, a different output shape, or a custom username search pipeline built around your own data? Get in touch at scraperhubapi@gmail.com and describe what you need.

If the Watson Username Finder saves you time, please leave a review on the Actor page. Ratings and written feedback directly shape which platforms and features get added next.

---

⚖️ Disclaimer

This username finder collects only publicly accessible information — it checks whether a public profile page exists at a given address and returns that address. It does not log in to any platform, bypass authentication, access private profiles, or retrieve any content behind a login wall.

You are responsible for how you use the data this scraper produces. Username search results can relate to identifiable individuals, so if you process them in a jurisdiction covered by the GDPR, the UK GDPR, the CCPA or similar privacy legislation, you must establish a lawful basis, honour data-subject rights, apply appropriate retention limits and keep the data secure. Using username enumeration for harassment, stalking, doxxing or any form of targeted intimidation is prohibited.

Respect the terms of service of every platform whose profiles you check, and comply with all applicable laws and regulations in your jurisdiction. A handle appearing in these results is evidence of a public page existing, not proof that a specific person owns it.

If you believe data about you has been collected through this Actor and you would like it removed, contact scraperhubapi@gmail.com with the details and we will action the request.