One question, one answer
BLOCK, REVIEW or NO_FRAUD_FOUND, with the reasons and the report. There is no ALLOW: finding no fraud is not a guarantee, and we don’t sell it as one.
A feed over API for registrars and security teams. Every domain arrives with the evidence behind its verdict, and if we correct one, the correction reaches you too.
Illustrative investigation workflow
Database inventory · 22 September 2026. Includes legitimate, suspicious and fraudulent assessments; counts are not verified attacks.
Visa, Mastercard, Google and OpenAI already let an agent prove who it is and that it may pay. None of them tells it whether the shop is a scam. That is our job, and now the agent can ask us before it pays.
BLOCK, REVIEW or NO_FRAUD_FOUND, with the reasons and the report. There is no ALLOW: finding no fraud is not a guarantee, and we don’t sell it as one.
Every answer carries a hash of the evidence. Keep it with the payment and, if there is ever a dispute, you can show what we told you and why.
The website, the API and the MCP read the same analysis. We won’t tell you one thing here and another there.
POST /api/v1/agent/merchant-check/
{"domain": "example-shop.com", "amount": 150, "currency": "EUR"}
{
"recommendation": "BLOCK",
"verdict": "FRAUDULENT",
"risk_score": 97,
"reasons": [
"105 of 165 domains on its server are flagged",
"Domain registered 2 days ago"
],
"report_url": "https://desenmascara.me/analisis/…",
"evidence_sha256": "658140d0ac2bc4b2…"
}Try the feed, plug it into your system, or send us a report and get the campaign back.
For registrars & security vendors
Plug the feed into your system and compare what arrives with what you already have.
For abuse teams, platforms & security providers
Sites that scam consumers, inside your workflow.
For abuse & incident response teams
From the domain you were sent to every one built alongside it.
Understand the observations and reasoning behind an assessment, with uncertainty kept visible.
Explore previous assessments where available. A past finding and a current threat are different things.
Use shared signals to guide investigation. A technical connection alone does not prove common ownership.
Tell us about your workflow. We’ll discuss fit, available evidence and a practical starting point.
Or email [email protected]Opens your email app. Nothing is submitted on this page.
Yes. Ask for trial access to the feed. We agree on the duration, intended use and scope before starting.
We correct it, and the correction arrives through the same feed so you can undo whatever you did with it. Any site owner can also dispute a verdict free of charge.
Coverage varies by domain and assessment date. We will establish which records and evidence are available for your use case.
Discuss your intended use with us. API access does not automatically include redistribution; source permissions and licensing scope must be agreed.
Engagements begin with agreed scope and availability. Assessments support investigation; they do not guarantee fraud prevention, complete coverage or takedown.