# Username Profile Finder (`fetch_cat/username-profile-finder`) Actor

Find public profile pages for usernames across curated websites with per-platform status diagnostics.

- **URL**: https://apify.com/fetch\_cat/username-profile-finder.md
- **Developed by:** [Hanna Nosova](https://apify.com/fetch_cat) (community)
- **Categories:** Social media, Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.14 / 1,000 item extracteds

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/actors/running/actors-in-store.md#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

## Username Profile Finder

Find public profile pages for one or more usernames across a curated set of social, developer, publishing, and community websites. This public profile finder is a practical username checker when you need exportable evidence rather than a manual browser search.

Use this Actor for brand monitoring, OSINT triage, trust and safety checks, recruiting research, lead enrichment, or manual impersonation audits where you need structured public profile-existence evidence instead of screenshots or one-off browser checks.

### At a glance

- **Primary job**: Check whether a handle has observable public profile pages on selected platforms.
- **Input**: Usernames plus an optional platform allowlist, output mode, concurrency, and timeout controls.
- **Output**: One dataset row per saved profile/check with status, HTTP code, final URL, detection method, timing, and rule metadata.
- **Best for**: Public profile discovery, brand handle audits, manual OSINT workflows, and repeatable exports to CSV, JSON, Excel, API, or automations.

### Who is it for?

- **Brand and trust teams** checking whether public handles appear across selected websites.
- **Recruiters and researchers** building a small, auditable set of public profile links from known usernames.
- **Developers and analysts** who need structured status rows rather than manual browser checks.

### Common workflows

- **Profile discovery**: Enter one handle and get confirmed public profile URLs across the curated default platforms.
- **Brand monitoring**: Check brand, product, or executive handles and compare repeat runs manually.
- **Trust and safety triage**: Export all statuses to see which checks were found, not found, blocked, or uncertain.
- **Lead/recruiting research**: Enrich a short list of public usernames with developer and community profile URLs.

### Ready-to-run examples

Open a public example to inspect its input, run it, or reuse it as a task:

- [Export Username Platform Statuses](https://apify.com/fetch_cat/username-profile-finder/examples/export-username-platform-statuses)
- [Check Brand Username Presence](https://apify.com/fetch_cat/username-profile-finder/examples/check-brand-username-presence)
- [Find Public Username Profiles](https://apify.com/fetch_cat/username-profile-finder/examples/find-public-username-profiles)

### What data can you extract?

| Field | Description |
| --- | --- |
| `username` | Original input username. |
| `normalizedUsername` | Username after trimming whitespace and leading `@`. |
| `platform` / `platformKey` | Human-readable platform name and stable platform key. |
| `platformDomain` | Domain checked for the platform. |
| `profileUrl` | Public profile URL template filled with the username. |
| `found` | Boolean indicating a confirmed public profile match. |
| `status` | `found`, `not_found`, `blocked`, `skipped`, `invalid_username`, `timeout`, `error`, or `unknown`. |
| `httpStatus` | HTTP status code when a request was made. |
| `finalUrl` | Final URL after redirects, when available. |
| `detectionMethod` | Rule used to classify the result. |
| `matchedPattern` | HTTP code, text pattern, or regex that influenced classification. |
| `category` / `isNsfw` | Platform metadata from the bundled rules. |
| `elapsedMs` | Milliseconds spent on the check. |
| `errorType` / `errorMessage` | Request error details for timeout/error rows. |
| `checkedAt` | ISO timestamp for the check. |
| `rulesVersion` | Bundled rule snapshot version. |

### Input configuration

| Setting | JSON key | Use it for | Example |
| --- | --- | --- | --- |
| Usernames | `usernames` | Handles to check; leading `@` is removed. | `["octocat", "github"]` |
| Platforms | `platforms` | Optional allowlist of supported platform keys. | `["github", "npm"]` |
| Output mode | `outputMode` | Save only found profiles or every check status. | `"foundOnly"` |
| Maximum platforms | `maxPlatforms` | Cap checks per username. | `10` |
| Maximum concurrency | `maxConcurrency` | Parallel platform checks. | `5` |
| Timeout seconds | `timeoutSecs` | Per-platform request timeout. | `8` |
| Include rule metadata | `includeRuleMetadata` | Keeps metadata fields in output. | `true` |

### Example input

```json
{
  "usernames": ["octocat"],
  "platforms": ["github", "gitlab", "npm", "hackernews", "devto"],
  "outputMode": "foundOnly",
  "maxPlatforms": 5,
  "maxConcurrency": 3,
  "timeoutSecs": 8,
  "includeRuleMetadata": true
}
```

### Example output

```json
{
  "username": "octocat",
  "normalizedUsername": "octocat",
  "platform": "GitHub",
  "platformKey": "github",
  "platformDomain": "github.com",
  "profileUrl": "https://github.com/octocat",
  "found": true,
  "status": "found",
  "httpStatus": 200,
  "finalUrl": "https://github.com/octocat",
  "detectionMethod": "http_status_final_url",
  "matchedPattern": "200",
  "category": "developer",
  "isNsfw": false,
  "elapsedMs": 542,
  "errorType": null,
  "errorMessage": null,
  "checkedAt": "2026-07-25T08:15:04.000Z",
  "rulesVersion": "2026-07-25-curated-v1"
}
```

### Pricing

The Actor charges when a run starts and once for each saved profile or requested check-diagnostic row. `foundOnly` charges only for confirmed profile rows; `allChecks` also saves and charges for the requested diagnostic rows. See the [live Apify Pricing tab](https://apify.com/fetch_cat/username-profile-finder/pricing) for current rates and volume tiers.

### Tips for best results

- **Start with found-only mode**: It keeps datasets focused on confirmed public profile URLs.
- **Use all-checks mode for audits**: It records blocked and not-found checks so you can see coverage gaps.
- **Keep lists bounded**: Public websites may throttle broad sweeps, so use focused usernames and platform sets.
- **Read statuses carefully**: `blocked`, `unknown`, or `timeout` does not mean a username is available; it means the public check could not confirm a profile.

### API usage

Node.js:

```js
import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor("fetch_cat/username-profile-finder").call({
  usernames: ["octocat"],
  platforms: ["github", "npm", "devto"],
  outputMode: "foundOnly",
  maxPlatforms: 3
});
console.log(run.defaultDatasetId);
```

Python:

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("fetch_cat/username-profile-finder").call(run_input={
    "usernames": ["octocat"],
    "platforms": ["github", "npm", "devto"],
    "outputMode": "foundOnly",
    "maxPlatforms": 3,
})
print(run["defaultDatasetId"])
```

cURL:

```bash
curl -X POST "https://api.apify.com/v2/acts/fetch_cat~username-profile-finder/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"usernames":["octocat"],"platforms":["github","npm","devto"],"outputMode":"foundOnly","maxPlatforms":3}'
```

### MCP and AI agents

Use this Actor from MCP-compatible tools through the official Apify MCP Server.

```bash
claude mcp add --transport http apify "https://mcp.apify.com?tools=fetch_cat/username-profile-finder"
```

JSON config example:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/username-profile-finder"
    }
  }
}
```

Example prompt: "Run Username Profile Finder for octocat on GitHub, npm, and DEV, then summarize found profile URLs and blocked checks."

### Limits and caveats

- **Public-only**: This Actor checks public profile pages only. It does not use credentials or access private account data.
- **Not an availability guarantee**: A not-found or blocked status must not be treated as proof that a username can be registered.
- **Platform blocking varies**: Some websites return 403, challenges, redirects, or soft-404 pages; those are recorded as diagnostic statuses.
- **Curated V1 coverage**: V1 uses a smaller high-confidence rule set rather than claiming exhaustive Sherlock/Maigret coverage.

### Legality and responsible use

Process only data you are allowed to access. Follow website terms, Apify's terms, and applicable laws. Do not use this Actor for harassment, credential attacks, private enrichment, or breach/leak workflows.

### Related actors

- [Website Contact Finder](https://apify.com/fetch_cat/website-contact-finder)
- [Website Social Profile Finder](https://apify.com/fetch_cat/website-social-profile-finder)
- [GitHub Profile Scraper](https://apify.com/fetch_cat/github-profile-scraper)
- [LinkedIn Jobs Scraper](https://apify.com/fetch_cat/linkedin-jobs-scraper)
- [Google Maps Lead Finder](https://apify.com/fetch_cat/google-maps-lead-finder)

### FAQ

#### Why did a known profile show as blocked or unknown?

The website may have returned a challenge, redirect, temporary error, or response that the V1 rule cannot safely classify. The Actor avoids false positives from blocked or uncertain pages.

#### Can I export results?

Yes. Apify datasets support JSON, CSV, Excel, XML, RSS, and API access.

### Support

Open an issue from the Actor page if a run fails or output looks wrong. Include the run ID or run URL, input JSON, expected output, actual output, and one reproducible public URL or username/platform pair.

# Actor input Schema

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

One or more usernames/handles to check. Leading @ symbols are removed automatically.

## `platforms` (type: `array`):

Optional platform keys to check. Leave empty for the curated default set.

## `outputMode` (type: `string`):

Save only confirmed found profiles, or save one row for every platform check with diagnostics.

## `maxPlatforms` (type: `integer`):

Maximum number of platform rules to check per username.

## `maxConcurrency` (type: `integer`):

Number of platform checks to run in parallel. Keep low to reduce blocking risk.

## `timeoutSecs` (type: `integer`):

Maximum time for one platform request before it is recorded as timeout.

## `includeRuleMetadata` (type: `boolean`):

Reserved for compatibility; V1 always includes platform category, domain, NSFW flag, and rules version.

## Actor input object example

```json
{
  "usernames": [
    "octocat"
  ],
  "platforms": [
    "github",
    "gitlab",
    "npm",
    "hackernews",
    "devto"
  ],
  "outputMode": "foundOnly",
  "maxPlatforms": 10,
  "maxConcurrency": 5,
  "timeoutSecs": 8,
  "includeRuleMetadata": true
}
```

# Actor output Schema

## `profileChecks` (type: `string`):

No description

## `summary` (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": [
        "octocat"
    ],
    "platforms": [
        "github",
        "gitlab",
        "npm",
        "hackernews",
        "devto"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("fetch_cat/username-profile-finder").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": ["octocat"],
    "platforms": [
        "github",
        "gitlab",
        "npm",
        "hackernews",
        "devto",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("fetch_cat/username-profile-finder").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": [
    "octocat"
  ],
  "platforms": [
    "github",
    "gitlab",
    "npm",
    "hackernews",
    "devto"
  ]
}' |
apify call fetch_cat/username-profile-finder --silent --output-dataset

```

## MCP server setup

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

```

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/Ygsy5E2KA1nRPrfjC/builds/4ql2GgME83qIw786c/openapi.json