News - Increasing Free Tier Limits on EasyEmailAPI

When we introduced authenticated access to the EasyEmailAPI free tier, the goal was to make the service more reliable and fair for everyone using it in real production flows. Since then, we’ve been closely watching how the API is being used. At its core, EasyEmailAPI focuses on email validation done right. Instead of stopping at basic format checks, it evaluates whether an address is realistically usable in real systems. That includes verifying domain DNS and MX records, detecting disposable a...

Written by
Mahdi Hezaveh
Published
Reading time
1 min

When we introduced authenticated access to the EasyEmailAPI free tier, the goal was to make the service more reliable and fair for everyone using it in real production flows.

Since then, we’ve been closely watching how the API is being used.

At its core, EasyEmailAPI focuses on email validation done right. Instead of stopping at basic format checks, it evaluates whether an address is realistically usable in real systems. That includes verifying domain DNS and MX records, detecting disposable and temporary email providers, identifying role-based addresses, and applying deliverability signals that help determine whether an inbox is likely to accept mail. The goal is not just to say whether an email looks valid, but to help teams prevent fake signups, reduce bounce rates, and keep their data clean from the very first request.

What we’re seeing is encouraging. Free accounts aren’t just testing endpoints, they’re validating real user signups, protecting checkout flows, and cleaning up inbound data before it reaches databases. In many cases, the free tier is already part of live systems.

Because of that, we’ve decided to increase the free tier rate limit.

As of today, free accounts can make up to 30 requests per minute, up from the previous limit of 10.

This change is meant to remove unnecessary friction for smaller projects and early-stage products, while keeping the service predictable and stable for everyone. For many signup flows, 30 requests per minute is enough to cover real usage without workarounds or batching.

The API itself doesn’t change. Existing integrations continue to work exactly as before. If you’re already authenticated, the higher limit is applied automatically to your account.

We’ll continue to adjust limits thoughtfully as usage grows and patterns become clearer. The goal is not to artificially constrain the free tier, but to make sure it remains useful, sustainable, and honest about what it offers.

More from the blog

Introducing centralized support across Empinet products

We’ve launched a single support hub for all Empinet products. You can now reach it from your product dashboard with automatic sign-in.

Read more

Catch-All Detection & SMTP Verification

If you've ever cleaned an email list and still ended up with unexpected bounces, you already know the problem. An email address can look perfectly valid. It can pass format checks. The domain can have proper MX records. Everything seems fine… until you actually send. That gap between "looks valid" and "actually deliverable" is exactly why we added Catch-All Detection and full SMTP checks to the PRO plan. Because basic validation just isn't enough anymore. The Catch-All Problem Nobody Talks A...

Read more

Ready to build something together?

Get in touch with our engineering team to discuss your next project.