Social Media Profile Finder
Find possible public social media profile URLs associated with submitted names or nicknames, with the source name and platform retained in each record.
Aperçu
Social Media Profile Finder turns a list of names, nicknames, handles, or brand names into a structured review set of possible public profiles. Each result keeps the submitted value beside a social-platform label and the profile address returned for that search, making scattered profile-search results easier to compare in one place.
The dataset is designed for discovery and triage rather than identity confirmation. It can help researchers, brand-protection teams, recruiters, and creator-research teams assemble candidates for further review while preserving the exact search value that produced each result. Keeping that context attached is especially useful when the same nickname appears on several platforms or belongs to multiple people.
Data notes
Records come from publicly searchable profile surfaces supported by the source workflow. Each record represents the outcome for one submitted value on one reported social platform. A returned profile address is a possible match, not proof that the profile belongs to the intended person, organization, or brand. The same submitted value can therefore produce multiple platform records, and every candidate should be independently reviewed before it is used for outreach, screening, enforcement, or attribution.
“Profile URL” can contain the literal value None when a platform row is returned without a matched address. Such rows are retained because they show which submitted value and platform were checked; they should not be treated as discovered profiles. Private, deleted, restricted, and sign-in-only profiles are outside the dataset’s public-search scope. Availability can also change as platforms and public profiles change.
What the results look like
Each record is one submitted value paired with a reported platform and its candidate profile address or no-match marker:
| Submitted name | Social platform | Profile URL |
|---|---|---|
| 1 | GitHub | https://github.com/1 |
| 1 | Medium | None |
| 1 | Twitch | https://www.twitch.tv/Ssaab |
Use cases
- For cross-platform name research, group rows by “Submitted name” and compare “Social platform” with “Profile URL” to see where possible public profiles were returned.
- For candidate review queues, filter out
Nonein “Profile URL,” then open the remaining addresses and verify whether their visible details match the intended subject. - For brand or handle monitoring, rerun the same “Submitted name” values at different times and compare “Social platform” and “Profile URL” to identify newly returned or changed candidates.
- For collision analysis, compare repeated “Submitted name” values against their “Profile URL” results to flag names that require additional evidence before attribution.
Périmètre et limites
Each run accepts 1 to 1,000 names or nicknames and searches supported public profile surfaces; retrieval is capped at 10,000 returned records per run.
- Adapté pour
- Use it when you need possible public profile URLs associated with one or more names, nicknames, handles, or brand names.
- Use it to build a review list that keeps each submitted value connected to the platform and candidate profile URL returned for it.
- À ne pas utiliser pour
- Do not use it as proof that a returned profile belongs to a specific person or organization; candidate matches require independent verification.
- Do not use it for private, deleted, restricted, or sign-in-only profiles because only publicly searchable profile surfaces are covered.
Gestion des échecs
Comportement en cas d'échec et de nouvelle tentative déclaré par l'auteur. Nous vous recommandons de l'inclure dans votre prompt système lors de l'intégration.
- 1If a run stops before completion, retry the same small input once; if it stops again, split a large name list into smaller runs.
- 2A missing profile URL can mean no public candidate was found for that name and platform or access was temporarily limited; review other returned platforms and retry later if needed.
Entrée
Paramètres requis pour appeler cette App, générés à partir de l'input.schema du manifest.json.
| Champ | Nom métier | Type | Requis | Défaut | Énum / Contraintes | Exemple | Description |
|---|---|---|---|---|---|---|---|
| names_or_nicknames | Names or nicknames | array<string> | Oui | — | jusqu'à 1000 éléments | ["1"] | Names, nicknames, handles, or brand names to search across supported public profile surfaces. Enter 1 to 1,000 values, with one value per item. |
Sortie
Structure des champs d'un enregistrement, générée à partir de l'output.schema du manifest.json.
| Champ | Nom métier | Type | Exemple | Description |
|---|---|---|---|---|
| input_name | Submitted name | string | 1 | Original name or nickname submitted for the profile search. |
| social_media | Social platform | string | GitHub | Platform label associated with the profile-search result. |
| profile_url | Profile URL | string | https://github.com/1 | Candidate public profile address returned for the submitted name and platform, or the literal value None when no address was returned. |
Schema de l'enregistrement
La sortie est renvoyée enregistrement par enregistrement. detail.output.idFieldHint
{
"type": "object",
"properties": {
"input_name": {
"type": "string",
"title": "Submitted name",
"description": "Original name or nickname submitted for the profile search.",
"prefill": "1"
},
"social_media": {
"type": "string",
"title": "Social platform",
"description": "Platform label associated with the profile-search result.",
"prefill": "GitHub"
},
"profile_url": {
"type": "string",
"title": "Profile URL",
"description": "Candidate public profile address returned for the submitted name and platform, or the literal value None when no address was returned.",
"prefill": "https://github.com/1"
}
},
"required": [],
"additionalProperties": false
}Intégration
Cette App peut être intégrée via MCP, API, SDK ou export de fichiers — tous les canaux partagent les mêmes capacités et la même tarification. Chaque requête s'authentifie avec l'en-tête Authorization: Bearer à l'aide d'une API Key (longue durée, créée dans la console Open Platform) ; les clients MCP peuvent aussi se connecter via OAuth, sans clé. D'autres options comme la CLI et Skill arrivent bientôt.
Avec MCP (Model Context Protocol), vous pouvez appeler cette App directement depuis des clients IA comme Claude et Cursor. Choisissez votre client et votre mode d'authentification, puis copiez la config ci-dessous.
Config du client
Remplacez la valeur après Bearer par votre API Key longue durée. Fonctionne dans n'importe quel client, en CI ou en environnement sans navigateur.
{
"mcpServers": {
"YiJacobJohnRaku__social-media-finder": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=YiJacobJohnRaku/social-media-finder",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Laissez l'IA tout configurer pour vous
Vous ne voulez pas modifier les configs à la main ? Copiez le prompt d'installation et collez-le dans n'importe quel client IA — il effectuera la configuration à sa manière. (Le prompt demande à l'IA de vous réclamer votre API Key, afin que les identifiants ne finissent jamais dans l'historique de conversation ni dans des configs partagées.)
detail.access.mcp.composeHint
Tarifs
Facturé selon le nombre d'enregistrements renvoyés avec succès. Les tâches échouées ne sont pas facturées.
Plusieurs événements de facturation se cumulent indépendamment — voir chaque élément pour les détails. Les tâches échouées ne sont pas facturées.
Essayer maintenant
Renseignez les paramètres et lancez l'exécution — les résultats proviennent d'un appel réel.