Username Lookup Across 400+ Social Platforms: one-request API, MCP and n8n

{
  "mode": "lookup",
  "usernames": [
    "torvalds"
  ],
  "coverage": "verified",
  "platforms": [
    "GitHub",
    "YouTube",
    "TikTok",
    "Pinterest",
    "X/Twitter",
    "Bluesky",
    "Steam"
  ],
  "maxConcurrency": 12,
  "maxResults": 10
}

---
name: username-lookup-across-400-plus-social-platforms
description: "One record per username/platform check with existence status, confidence, evidence, HTTP status and optional profile metadata, plus a run summary record. Runs the Apify Actor nimbryxo-studio/username-lookup-across-400-plus-social-platforms. Use when the user needs Username data with fields such as recordType, query, platform, url, exists, status and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/username-lookup-across-400-plus-social-platforms"
  store-url: "https://apify.com/nimbryxo-studio/username-lookup-across-400-plus-social-platforms"
---

# Username Lookup Across 400+ Social Platforms

Use this skill to fetch Username data with the Apify Actor `nimbryxo-studio/username-lookup-across-400-plus-social-platforms` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `lookup`, `availability`, `name_search`, required | lookup returns found profiles (plus blocked/unknown checks), availability returns one row per platform with available/taken/unknown, and name_search generates handle candidates from a full name. |
| `usernames` | array | Handles to check. Accepts plain handles, @handles and profile URLs. Required for lookup and availability. Maximum 50 per run (10 when extended coverage is active). |
| `coverage` | one of `verified`, `extended` | verified uses the 29 platforms that passed a known-handle plus random-handle gate. extended adds 400+ best-effort platforms at low confidence. |
| `platforms` | array | Limit the run to specific platforms. Leave empty to use all verified platforms, or all verified + extended platforms when coverage=extended. Extended-only platform names are rejected when coverage=verified. |
| `maxConcurrency` | integer | Concurrent checks. The default of 12 is the validated safe value for the verified set; per-host requests are limited further. |
| `maxResults` | integer | Maximum profile/check rows to emit. The summary row is always emitted and is not counted. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "lookup",
  "usernames": [
    "torvalds"
  ],
  "coverage": "verified",
  "platforms": [
    "GitHub",
    "YouTube",
    "TikTok",
    "Pinterest",
    "X/Twitter",
    "Bluesky",
    "Steam"
  ],
  "maxConcurrency": 12,
  "maxResults": 10
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~username-lookup-across-400-plus-social-platforms/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~username-lookup-across-400-plus-social-platforms/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `recordType`, `query`, `platform`, `url`, `exists`, `status`, `availability`, `confidence`, `evidence`, `httpStatus`, `displayName`, `matchScore`, `mode`, `coverage`, `queriesChecked`, `platformsChecked`, `profilesFound`, `notFound`, `unknown`, `rows`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.