# Maigret Username Scraper - Accounts Across 1490+ Sites (`scrapesage/maigret-scraper`) Actor

Hunt a username across 1,490+ social networks and websites with the Maigret OSINT database. Returns every site where an account exists, the profile URL, the category, and a discrimination-verified match status. Filter by category. No login, no key. Export JSON, CSV, Excel.

- **URL**: https://apify.com/scrapesage/maigret-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Social media, Automation, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.20 / 1,000 account founds

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

## Maigret Username Scraper - Accounts Across 1,490+ Sites

Hunt a **username across 1,490+ social networks and websites** using the **Maigret** OSINT site database - the deep net for username investigations. For each handle you get every site where an account exists, the **profile URL**, the **site category**, and a **discrimination-verified** match status that suppresses false positives.

Filter by category, check up to 100 handles at once. No login, no API key.

### What it does

- Checks a username against **1,490+ sites** across 46 categories (social, coding, gaming, crypto, forums, photo, business, and more).
- Returns the sites where an **account exists**, each with the direct **profile URL** and its **category**.
- **Verifies every hit** (`verifyClaims`, on by default): re-checks each positive with a decoy handle and drops sites that can't distinguish a real account - so "found" means found.
- **Category filter** - restrict the hunt to, say, only `coding` or `crypto` sites.
- Optional **full per-site audit** (`includeUnclaimed`) for username-availability research.

### Sherlock vs Maigret

Use **[Sherlock Username Scraper](https://apify.com/scrapesage)** for a fast pass over ~481 well-known sites. Use **Maigret** when you want the widest possible net (1,490+ sites) and category filtering. Same verified-match engine underneath.

### Example output

```json
{
  "type": "account",
  "username": "torvalds",
  "site": "GitHub",
  "category": "coding",
  "url": "https://github.com/torvalds",
  "status": "claimed",
  "detectionType": "message",
  "httpStatus": 200,
  "source": "maigret",
  "checkedAt": "2026-08-27T05:30:00.000Z"
}
```

| Field | Meaning |
|---|---|
| `username` | The handle that was checked |
| `site` | Site / network name |
| `category` | Site category (social, coding, gaming, crypto, ...) |
| `url` | Direct profile URL for that handle |
| `status` | `claimed` (account exists), or `available` / `unknown` when *Include unclaimed* is on |
| `detectionType` | How the site was checked: `status_code`, `message`, or `response_url` |
| `httpStatus` | HTTP status returned by the site |

### Input

| Field | Description |
|---|---|
| **Usernames** | Handles to hunt (up to 100). |
| **Max sites per username** | How many of the 1,497 sites to check per handle (most-characterized first). |
| **Site categories** | Optional filter - only check sites in these categories. |
| **Verify claims** | Re-check positives with a decoy handle to kill false hits (recommended). |
| **Include unclaimed / unknown sites** | Also output where the handle was NOT found - full audit. |
| **Include adult (NSFW) sites** | Off by default. |
| **Proxy** | Residential proxies improve coverage. |

### Use cases

- **OSINT & investigations** - map the full online footprint of a handle.
- **Brand protection** - find impersonation accounts across the web.
- **Username availability** - see where a new handle is still free.
- **Profile enrichment** - resolve a handle to its profile URLs, by category.

### Notes on accuracy

Username hunting is best-effort. `claimed` means the site's "not found" signal was absent and (with *Verify claims* on) the site could tell a real handle from a decoy. Sites that block datacenter IPs are reported as `unknown`, not guessed - use residential proxies for the widest coverage. A larger **Max sites per username** = more coverage but longer runs.

### Run it from an agent (MCP / API)

Agent-ready: typed input schema, structured JSON output. An LLM agent or automation can call this Actor over the Apify API / MCP to answer "where does this username exist?" in one step. Pass `usernames` (optionally `tags`) and read the `account` records back.

### FAQ

**Login or API key?** No - public presence signals only.
**Will it find every account?** No tool can. Maigret maximizes coverage (1,490+ sites) and is honest about what it can't determine (`unknown`).
**Is this legal?** It checks publicly observable existence signals. Use the results in line with each site's terms and applicable law.

# Actor input Schema

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

One or more usernames / handles to hunt across 1,490+ sites, e.g. <code>johnsmith</code>, <code>elonmusk</code>. Up to 100 per run.

## `maxSitesPerUsername` (type: `integer`):

How many sites to check per handle (up to 1497). The most-characterized sites are checked first; raise for full coverage, lower for faster/cheaper runs.

## `tags` (type: `array`):

Only check sites in these categories. Leave empty to check all categories.

## `verifyClaims` (type: `boolean`):

Re-check every positive with a decoy handle and drop sites that cannot tell accounts apart (kills false positives). Slightly more requests, much higher precision.

## `includeUnclaimed` (type: `boolean`):

Also output sites where the username was NOT found or could not be determined (full per-site audit). Off = only sites where an account exists.

## `includeNsfw` (type: `boolean`):

Include adult-content sites in the check. Off by default.

## `proxyConfiguration` (type: `object`):

Proxies used for the checks. Residential proxies improve coverage because some sites block datacenter IPs (returning 'unknown').

## Actor input object example

```json
{
  "usernames": [
    "johnsmith"
  ],
  "maxSitesPerUsername": 500,
  "verifyClaims": true,
  "includeUnclaimed": false,
  "includeNsfw": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All account records as JSON items in the default dataset.

# 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": [
        "johnsmith"
    ],
    "maxSitesPerUsername": 500,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/maigret-scraper").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": ["johnsmith"],
    "maxSitesPerUsername": 500,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/maigret-scraper").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": [
    "johnsmith"
  ],
  "maxSitesPerUsername": 500,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call scrapesage/maigret-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/maigret-scraper"
        }
    }
}

```

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/MLz6L74gofn9NozOP/builds/KJ52bfflsHaadbN3W/openapi.json