<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: rehaanhassan</title>
    <description>The latest articles on Forem by rehaanhassan (@rehaanhassan).</description>
    <link>https://forem.com/rehaanhassan</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3520334%2F7293aff3-b5d3-44c2-90fc-01cd59672f47.png</url>
      <title>Forem: rehaanhassan</title>
      <link>https://forem.com/rehaanhassan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/rehaanhassan"/>
    <language>en</language>
    <item>
      <title>Show HN: AI-Powered Email Verification API with ML Risk Scoring + 50% Off for RapidAPI Users</title>
      <dc:creator>rehaanhassan</dc:creator>
      <pubDate>Sun, 21 Sep 2025 20:59:28 +0000</pubDate>
      <link>https://forem.com/rehaanhassan/show-hn-ai-powered-email-verification-api-with-ml-risk-scoring-50-off-for-rapidapi-users-4p6f</link>
      <guid>https://forem.com/rehaanhassan/show-hn-ai-powered-email-verification-api-with-ml-risk-scoring-50-off-for-rapidapi-users-4p6f</guid>
      <description>&lt;p&gt;Hey HN! I built an email verification API that actually does more than check if an email looks valid. It combines machine learning risk scoring with real SMTP validation to give you better insight into email quality.&lt;br&gt;
What's Different&lt;br&gt;
Most email validators just tell you "valid" or "invalid". Mine gives you a risk score, explains why, AND tells you whether you should actually send to that email. Like "Don't send - suspicious due to new domain registration" or "Safe to send - verified corporate email". Plus it does the usual SMTP checks - MX records, mailbox verification, catching disposables and role accounts.&lt;br&gt;
The bulk verification handles large lists without timing out, which was a pain point I had with other services.&lt;br&gt;
Why Risk Scoring + Reasoning&lt;br&gt;
Basic verification: "Does this email exist?"&lt;br&gt;
With risk scoring + explanations: "Should I trust this email, and here's exactly why you might not want to."&lt;br&gt;
Having the reasoning helps with:&lt;/p&gt;

&lt;p&gt;Manual review decisions (you know what to look for)&lt;br&gt;
Building automated rules for your specific use case&lt;br&gt;
Understanding patterns in your user base&lt;br&gt;
Explaining decisions to stakeholders&lt;/p&gt;

&lt;p&gt;Real-World Use Cases&lt;/p&gt;

&lt;p&gt;SaaS onboarding (auto-approve low risk, manual review high risk)&lt;br&gt;
E-commerce fraud prevention&lt;br&gt;
Cleaning marketing lists before campaigns&lt;br&gt;
User registration workflows&lt;/p&gt;

&lt;p&gt;Try It Out&lt;br&gt;
Playground: &lt;a href="https://rapidapi.com/rehaanhassan/api/ai-powered-email-verification-api/playground/apiendpoint_e126a9a9-f463-4f00-a2cc-f3ab51993994" rel="noopener noreferrer"&gt;https://rapidapi.com/rehaanhassan/api/ai-powered-email-verification-api/playground/apiendpoint_e126a9a9-f463-4f00-a2cc-f3ab51993994&lt;/a&gt;&lt;br&gt;
Docs/Tutorials: &lt;a href="https://rapidapi.com/rehaanhassan/api/ai-powered-email-verification-api/tutorials" rel="noopener noreferrer"&gt;https://rapidapi.com/rehaanhassan/api/ai-powered-email-verification-api/tutorials&lt;/a&gt;&lt;br&gt;
50% Off for RapidAPI Users&lt;br&gt;
If you're already on RapidAPI, I'm offering 50% off the Pro plan. Just drop your username here: &lt;a href="https://docs.google.com/forms/d/1_El6E2YOu5yvYYNbUE6I-l7544SJGBC3dzuIFOzJ0uY/edit" rel="noopener noreferrer"&gt;https://docs.google.com/forms/d/1_El6E2YOu5yvYYNbUE6I-l7544SJGBC3dzuIFOzJ0uY/edit&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Built this after getting burned by high false positive rates with existing tools. The ML component learns from validation patterns to be more nuanced than simple rule-based systems.&lt;br&gt;
What's your experience been with email validation? Always curious about edge cases people run into.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>tooling</category>
      <category>machinelearning</category>
    </item>
  </channel>
</rss>
