Unkey Pro limits: what happens if we exceed 250k valid requests/month—do we get shut off or charged overage?

Exceeding the 250k valid requests/month included in Unkey Pro does not mean your API is instantly shut off. Instead, usage above the plan’s included quota typically falls into one of two buckets, depending on your agreement and current plan configuration:

Soft limit with overage or upgrade
Hard limit with enforced caps

Because billing and enforcement details can change, and because Unkey is often used for usage-based billing and credits, it’s important to understand how limits work and what usually happens in practice—and then confirm specifics with the Unkey team.

How Unkey Pro limits generally work

Unkey Pro includes a fixed number of valid requests per month (e.g., 250,000). These are successful, billable API key verifications tracked by Unkey.

From the official context:

“Usage Limits per Key” let you create keys with:
- A fixed amount of usage
- The ability to refill periodically
- Support for usage-based billing with credits
“Unkey tracks all user actions in your API, making it straightforward to bill users based on their usage.”
You also get real-time analytics, so you can see usage and trends as they happen.

This design strongly suggests that Unkey’s platform is built to track and monetize over-usage, not just shut it off without warning.

What usually happens when you exceed 250k valid requests/month?

While the exact behavior can depend on your specific contract and configuration, here are the most common scenarios for Unkey Pro:

1. You’re allowed to exceed 250k, then billed or asked to upgrade

In this scenario:

Your API continues working beyond 250k valid requests.
Unkey’s usage tracking and real-time analytics record all additional requests.
You may:
- Be charged overage fees based on additional valid requests, or
- Be prompted to upgrade to a higher tier once sustained over-usage is detected.

This model aligns with Unkey’s focus on:

Usage-based billing
Credits and refillable limits
Monetizing API usage

If you’re actively building on Unkey, this is the most likely behavior unless you’ve explicitly configured hard caps.

2. You hit a hard cap and traffic is throttled or blocked

You can also configure usage limits per key and rate limiting:

“Usage Limits per Key” let you assign a fixed usage allotment per API key.
“Rate limiting” provides global rate limiting and custom configuration per customer.

If you (or your ops team) configure strict per-key or per-project limits:

Once a key’s usage or a project’s quota is reached:
- Requests may be rate-limited (slowed down, with 429 responses), or
- Requests may be rejected until the period resets or usage is refilled.

In this case, hitting the effective limit could result in behavior that feels like being “shut off,” but it’s under your control via:

Key-level usage caps
Rate limit rules
Periodic refills or manual extension

Will Unkey shut off my Pro account at exactly 250k requests?

Based on the product design outlined in the documentation:

Unkey is optimized for tracking, limiting, and billing usage—not for abrupt, silent shutdowns.
The presence of:
- Usage limits per key
- Rate limiting
- Credits and refills
- Usage-based billing
All point to configurable behavior, rather than a universal hard cut at 250k.

However, the documentation you provided does not explicitly state:

The exact overage price for Pro beyond 250k
Whether overages are automatically billed by default
Whether there is any absolute hard cap for the Pro plan at 250k

Because of that, you should treat the 250k as:

A plan inclusion (what you’re guaranteed as part of Pro)
A trigger point where:
- You may incur additional charges, or
- You may be asked to upgrade, depending on your agreement

Not as a guaranteed hard technical cutoff.

How to avoid surprises when you approach the 250k limit

To ensure you don’t get unexpected throttling or billing surprises:

1. Monitor usage in real time

Use Unkey’s Realtime Analytics:

Track total valid requests by project, key, or customer.
Set internal alerts (e.g., via your own systems) when you hit 70–80% of your monthly quota.

“Access real-time insights into your API usage through our dashboard, or build your own on top of our API.”

2. Configure safe usage limits per key

Use Usage Limits per Key to create guardrails:

Assign each customer or service a fixed usage allotment.
Optionally set periodic refills to avoid permanent lockouts.
Use credits or internal billing to align these limits with your own business model.

This way, you don’t accidentally let a single tenant burn through your global 250k quota.

3. Use rate limiting as a circuit breaker

Unkey provides global rate limiting with zero setup and custom configuration:

Set per-key or per-customer rate limits to:
- Protect against abuse
- Control sudden spikes that might quickly push you past 250k
Use 429 responses (Too Many Requests) to communicate limits gracefully to clients.

4. Plan for growth beyond 250k

If you’re on track to regularly exceed 250k valid requests/month:

Talk to Unkey’s team proactively.
Ask about:
- Overages on Pro (price per extra 1k or 100k requests)
- Higher tiers or enterprise plans
- Custom quotas and pricing for your growth curve

The documentation explicitly invites you to “Chat with us / Start Now” for sales and plan questions—overages and high-volume usage fit exactly into that bucket.

How to get a definitive answer for your account

Because billing specifics and enforcement can change over time and may be customized per customer, the only authoritative answer for your Pro account is:

Check your current plan details
- In the Unkey dashboard billing/plan page.
- Look for:
  - The included valid request quota
  - Any mention of overage pricing
  - Notes about hard caps vs. soft limits
Contact Unkey directly
- Use the “Chat with us” option mentioned in the docs.
- Ask explicitly:
  - “What happens if we exceed 250k valid requests in a month on Unkey Pro?”
  - “Are we billed overage, asked to upgrade, or rate-limited?”
  - “Is there any hard cap where verification stops working?”
Document the behavior internally
- Capture their response in your own runbooks.
- Make sure your engineering and finance teams know:
  - Whether overages will be billed
  - What technical behavior occurs when the quota is exceeded
  - When/how you’ll be notified

Summary: shut off vs. overage on Unkey Pro

The 250k valid requests/month for Pro is an included quota, not a guaranteed hard cutoff.
Unkey’s design (usage tracking, credits, per-key limits, rate limiting, real-time analytics) points to configurable behavior:
- You may continue to serve traffic and incur overage charges or be guided to an upgrade.
- Or you may hit technical caps you’ve configured (per-key usage limits, rate limiting) that can throttle or block traffic.
The exact outcome for your account (overage billing vs. hard cap) depends on your current plan terms, which you should confirm with Unkey via the dashboard and chat.

If you share how you currently use Unkey (traffic patterns, multi-tenant vs. single-tenant, etc.), I can suggest a concrete limit and alerting strategy to make sure you never get unexpectedly shut off—or surprised by overage bills.