See beyond the account in the report.
Search public sources from a reported game account, email, handle, or link. Bring the results into your review queue and keep the context for the next moderator.
A report is a starting point, not a verdict.
A player reports a copycat Epic account asking for gift cards. Resolve the reported display name, inspect available public account links, then compare them with your own platform evidence.
“This account is using the creator’s name and asking players to send gift cards.”
Epic Games
Resolve the reported display name
Check the account record
- Stable Epic account ID
- Compare with your report
- Linked accounts
- Review where available
Keep the review together
Save the source details and unresolved questions beside the original report. Your team makes the policy decision.
Not every report starts with a player name.
Some cases start with an email, a public handle, or a link. Search each identifier on its own terms; a shared name is a lead, not a confirmed identity.
A seller moves payment to email.
A buyer forwards the seller’s off-platform payment request.
Reported identifier
payments@shop.example
Email search
Inspect when available
Public profile · Displayed name · Source link
Compare any returned profile with the message the buyer supplied.
A handle appears in a harassment report.
A moderator receives the reported Discord username and screenshots.
Reported identifier
creator_support
Discord
Username search
Inspect when available
Public account · Profile details · Source link
Check the original profile and any stable ID against the report.
A giveaway link spreads through comments.
Several users report a site asking for their game login.
Reported identifier
rewards.example
Domain
Domain Intelligence
Inspect when available
Registration · DNS records · HTTP response
Inspect the live destination and domain records before acting.
Keep your review queue. Add the source context.
Send the emails, usernames, and domains from incoming reports to the Search API. Each completed check sends a signed webhook with the result, ready to attach to the originating report.
Reviewers see the public sources beside the original report. Your own signals and policy still decide the action.
Osintly Search API
Checks each identifier against available sources.
Your review queue
Available records return by signed webhook.
Let the next shift reopen the sources.
A night reviewer checks a reported account. The morning team can reopen the saved search, read the source details, and see what is still unverified.
Organization investigations hold searches, notes, and supplied files together. Every organization member can read its projects.
Questions from Trust & Safety teams.
Fit public-source checks into your review process.
Show us the reports your team reviews. We’ll help map the public checks, API volume, and shared workspace to your workflow.