Username
Use this lane when the starting point is a public label, handle, or account-style clue.
Overview
This lane is the best place to start when you already have a stable public label and want to see where it appears across open sources.
It is intended for quick validation, profile tracing, and account discovery.
Request
POST /osint/investigate/usernameBase URL: https://test.intelfetch.dev/api/v1
Authentication: send your Bearer token in the Authorization header.
Body
{
"topic": "example-handle",
"language": "en",
"country": "US",
"dateRange": "past_month",
"aliases": ["example handle"],
"usePython": false
}Fields
| Field | Required | Notes |
|---|---|---|
topic | Yes | The exact public label you want to inspect |
language | No | Helps narrow search results in some sources |
country | No | Adds regional context where supported |
dateRange | No | Useful when you want a recent pass |
aliases | No | Optional alternate labels |
usePython | No | Enables the Python-backed checks when available |
Response
The response is returned as a structured result envelope. For this lane, the most relevant sections are:
findingsusernameResults
findings is the main list to review first. usernameResults gives you the normalized account-level output when the backend finds matching profiles.
{
"findings": [
{
"title": "example-handle on ExampleSite",
"source": "Sherlock",
"type": "username_enumeration",
"url": "https://examplesite.com/example-handle",
"date": "2026-05-19T00:00:00Z"
}
],
"usernameResults": [
{
"platform": "ExampleSite",
"url": "https://examplesite.com/example-handle",
"found": true,
"statusCode": 200,
"displayName": "Example Handle",
"bio": "Public profile"
}
]
}How to use it well
- Start with the shortest version of the label you trust.
- Add one alias at a time if the result set is too small.
- Use a recent date range only when you are trying to reduce older noise.
- If the first pass is broad, refine the label instead of adding many filters at once.