How we're building a fraud-reporting experience with React, TypeScript, Supabase, and Gemini — and why human review matters more than a perfect-looking AI demo.

Imagine receiving this message:

"Your package couldn't be delivered. Pay €2.95 to arrange another delivery."

There's a link underneath it.

You don't recognize the sender. The website looks legitimate, but something feels wrong.

Now imagine opening a fraud-reporting website and seeing a form asking you to identify the incident category, communication channel, suspicious domain, financial impact, relevant evidence, and contact details.

For a developer, these fields probably make sense.

For someone who is worried about losing money, they might not.

That difference became an important part of what we're building at Axon OSINT .

We wanted people to report suspicious activity without first having to understand the vocabulary of fraud investigations.

And we started with something almost everyone knows how to create:

A screenshot.

But we…