Search one username across 3000+ sites with an API call (Maigret, hosted)

Description and use

The same Maigret search runs as an API call and returns structured rows: one row per registered site with site name, direct profile URL and status, plus optional profile fields and misses.

Problem

Checking a username across thousands of sites usually means running Maigret locally: install it, let it walk the site list, then clean up the console output.

Outcome

The same Maigret search runs as an API call and returns structured rows: one row per registered site with site name, direct profile URL and status, plus optional profile fields and misses.

Workflow

• Send an input object with usernames (array), topSites (limit to top N sites; 0 means all 3000+), tags/excludeTags, sites (fixed list), and noRecursion (skip follow-up searches on discovered usernames).
• Call the Apify Actor Maigret username search on Apify with the input payload.
• Pull the result as JSON or CSV from the API response and filter in code instead of grepping a console dump.
• Optionally enable extractProfileFields to also return public profile fields such as name, bio or location; use printNotFound to add misses to the output.
• Use only for public profile lookups on subjects you have a legitimate reason to check, and follow applicable laws.
• Request an added output field by commenting on the Actor if needed.
• Build similar Actors at Ntriq (Korea).

Evidence

Checking a username across thousands of sites usually means running Maigret locally: install it, let it walk the site list, then clean up the console output.

Source

One row per site where the handle is registered, each with the site name, a direct profile URL and the status.

Source

topSites: limit the search to the top N sites (0 means all 3000+, which is slower)

Source

Because it is a dataset, you can pull it as JSON or CSV from the API and filter in code instead of grepping a console dump.

Source