Maigret Username Scraper - Accounts Across 1490+ Sites
Pricing
from $2.20 / 1,000 account founds
Maigret Username Scraper - Accounts Across 1490+ Sites
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.
Pricing
from $2.20 / 1,000 account founds
Rating
0.0
(0)
Developer
Scrape Sage
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
19 days ago
Last modified
Categories
Share
Maigret Username Scraper - Accounts Across 1,490+ Sites
Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the Maigret open-source project. All trademarks mentioned are the property of their respective owners. "Maigret" is referenced only to describe the kind of check this Actor performs.
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
codingorcryptosites. - Optional full per-site audit (
includeUnclaimed) for username-availability research.
Sherlock vs Maigret
Use Sherlock Username Scraper 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
{"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.
Agent-ready: autonomous payments (x402 & Skyfire)
This actor is agent-ready — AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:
- x402 — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server — no account, no API key.
- Skyfire — agent-to-service payments for fully autonomous AI-agent workflows.
Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.
How much does it cost?
This Actor uses Apify's pay-per-event pricing: you are charged only for the results it delivers, with no monthly rental and no start fee. The events it can charge are:
- Account found - One account record - a site where the username was checked (default: found), with profile URL, category and verified status
The current price of each event is shown on the Pricing tab of this page. Set a maximum total charge on the run if you want a hard cap on spend, and use the input limits to control how much the Actor fetches.
Automate & schedule
Run this Actor on autopilot and pull results into your own stack:
- Apify API - start runs, fetch datasets and manage schedules over REST.
- apify-client for JavaScript and apify-client for Python - official SDKs.
- Schedules - run it hourly, daily or weekly and keep your dataset current.
- Webhooks - trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });const run = await client.actor('scrapesage/maigret-scraper').call({// your input - see the Input section above});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(`Got ${items.length} records`);
Integrate with any app
Connect the dataset to thousands of apps - no code required:
- Make - multi-step automation scenarios.
- Zapier - push new records straight into your CRM or spreadsheet.
- Slack - get notified when a scheduled run finds something new.
- Google Drive / Sheets - auto-export every run to a spreadsheet.
- Airbyte - pipe results into your data warehouse.
- GitHub - trigger runs from commits or releases.
More scrapers from scrapesage
Related Actors in the same category:
- Twitter (X) Scraper - Tweets, Profiles & Monitor
- Instagram Hashtag Scraper - Filtered Post Search
- LinkedIn Profile Scraper - People, Job Changes & B2B Leads
- LinkedIn Ad Library Scraper - Competitor B2B Ads & Creatives
- YouTube Scraper - Channels, Videos & Creator Leads
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.
Data & lawful use
You supply the input (usernames); the Actor only checks or enriches what you give it against publicly available sources. Make sure you collected that input lawfully and have a lawful basis to process it. This is a verification and open-source-intelligence tool for security research, fraud prevention and checking identifiers you are authorised to check. Do not use it to locate, track, profile or harass individuals, and follow the anti-spam and telemarketing rules that apply to you (for example GDPR and PECR in the EU and UK, CAN-SPAM and the TCPA in the US, CASL in Canada). Honour opt-outs and deletion requests.
Under Apify's Standard Actor Contract, which governs your use of this Actor, you are the controller of any personal data in your input and output and scrapesage acts only as your processor: that data is processed solely to run your job, written only to your own Apify storage, never used for any other purpose and never shared onward. If you need help with a data-subject request that involves this Actor's output, open an issue on the Issues tab.
Disclaimer
This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the Maigret open-source project. All trademarks mentioned are the property of their respective owners.
"Maigret" is referenced only in a descriptive, nominative sense - to describe the kind of check this Actor performs. This Actor is an independent implementation, is not an official Maigret product and is not authorised or certified by the Maigret open-source project. It collects only publicly available information; you are responsible for ensuring your use of that data complies with applicable laws and regulations.
Need help?
Open an issue on the Actor's Issues tab, or visit the Apify help center. Feature requests are welcome - this Actor is actively maintained.