How to stop multiple accounts on a free data API quota
Licensed data costs you per lookup, and repeat free quotas add up to a free bulk feed. What it costs, which basic fixes break and what holds up.
Hi, our month-end portfolio run failed again last night. About 9,000 of our 11,000 properties came back with 429 errors, and that's well inside the 12,000 lookups on our plan. This is the third month in a row. Our lender needs those numbers by Thursday, so I've been rerunning the failed ones by hand since 6 this morning. I like your data, but I can't keep calling this a blip, and my manager has asked me to price out the other provider. Is something going on at your end?
That message is a scenario, and the numbers below are assumptions to swap for your own.
You run a property data API. Developers send an address and get back the owner, the tax assessment and the sale history. You license those records, and say your supplier bills you $0.012 a lookup and caps you at 40 lookups a second across all your customers. Free accounts get 2,000 lookups a month, reset at midnight UTC on the 1st. The $299 plan includes 12,000, and the customer above is on it.
You pull the logs for midnight on the 1st. Their run is in there. So are 120 free accounts, each with a verified email, each under its quota, all starting the moment the quota came back. This is free API quota multiple accounts abuse from your side of the API: nothing is over a limit, and your paying customer still can't get through.
- 120 accounts × 2,000 lookups = 240,000 lookups
- 240,000 × $0.012 = $2,880 to your supplier, every month
- 120 keys × 2 requests a second (your per-key limit) = 240 requests a second, against a cap of 40
- 240,000 ÷ 40 = 6,000 seconds, or 100 minutes
For 100 minutes, free keys ask for six times what your supplier will serve, and the month-end run waits in the same line. Five requests in six bounce, which is how 11,000 properties turn into about 9,000 failures. Illustrative, with bars for requests asked (240 free, 10 your customer) and the line for your cap:
Say you have 60 customers on that plan, bringing in $17,940 a month (60 × $299). A customer who uses every lookup leaves you $155 after license costs ($299 minus 12,000 × $0.012). So the 120 accounts eat the full margin of 19 customers ($2,880 ÷ $155 = 18.6). Credit a month to the 14 customers whose runs failed and that's another $4,186 (14 × $299). You're down $7,066 this month ($2,880 plus $4,186), 39% of revenue.
Now delete all 120 accounts and see what stays.
The records stay. At 240,000 a month, a year of this is 2.88 million property records in someone else's database, a bulk feed you never sold. At list price that's 20 plans a month (240,000 ÷ 12,000), or $5,980 you didn't charge. You can't recall a single row, and if your license limits redistribution, your supplier's email will be addressed to you.
The contract stays too. Say your renewal sets next year's minimum from your peak volume. Real traffic is 564,000 lookups a month (504,000 paid and 60,000 free), which costs $6,768. The 120 accounts pushed you to 804,000, so the supplier commits you to 800,000, or $9,600 a month whether you use it or not. That's $2,832 a month for accounts you've already deleted, $33,984 across the year. Check your own contract.
So you're choosing between bad options. You can pay for a higher cap so free accounts finish sooner. You can cut the free tier to 500 lookups, and the developer testing an integration against 1,500 real addresses runs out on day one, while the same haul just takes 480 accounts (240,000 ÷ 500). Meanwhile, the customer with the lender deadline is pricing out the other provider. That's $3,588 a year ($299 × 12) walking out over something they never caused.
Why a free data API quota gets multiplied
Most free tiers give away something that gets used up. A data API gives away something people keep. A free compute minute is gone once it's spent, but a record pulled from your API stays in the caller's database, so every extra account adds to a pile. Enough accounts and the pile is the bulk file you'd normally license out under contract.
Your controls measure a different unit. The quota is counted per account and rate limits per key, so each of the 120 is only ever compared with itself, and each one passes. The cost lands on the same supplier invoice as every real lookup, which is why API free tier abuse can run for months before anyone goes looking.
The obvious fix is a rule: one free account per developer. Write that rule down, but it won't hold by itself, since a new account arrives with an empty meter. Limiting free API keys per developer has the same gap: it caps keys inside an account, and the next account brings its own. And plenty of second accounts are fine, like a consultant with three clients.
The basic checks for a free API quota, and how each one breaks
Each of these does catch something. Email comes first because every signup form has it. Unique-email rules only compare text, and one inbox can answer to many spellings: Gmail ignores dots, and plus-tagged mail reaches the same inbox. That's just how email works.
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | Any real second inbox | Developers whose code gets stuck in a company mail filter | Sending and deliverability work |
| Disposable-domain blocks | Known throwaway services | New domains and ordinary mailboxes | People using privacy forwarding | A list someone updates forever |
| Gmail dots and plus addressing | One Gmail inbox written several ways | A second real mailbox | People who share one inbox | Upkeep as mail services change |
| CAPTCHA | Simple scripts on the signup page | Signups done by hand, and every API call after | People using screen readers or privacy tools | Fees and lost signups |
| Phone or card requirement | Casual second accounts | Anyone with another number or card | Students, and staff waiting on a company card | Text charges and fewer first calls |
| One per IP address | Repeat signups on one connection | Any other network | Offices, bootcamps and hackathons | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Everything off your list | Staff on company VPNs | Another list to maintain |
| Rate limits per key | Bursts from one key | 120 keys under the limit | Real batch jobs | Tuning per endpoint |
| Manual review | What a person can spot | Anything spread out slowly | Whoever looks odd to a tired reviewer | Hours every month |
A developer comparing three providers in one afternoon signs up with whoever hands over a key in a minute, so a card, a phone number and a puzzle cost you integrations you'll never hear about. VPN blocks and IP rules do extra harm, because real developers call you from shared cloud and CI addresses. Reviewing 900 new free accounts a month at two minutes each is 30 hours, due again next month. And none of these signup checks touches the 120 accounts you already have, which get 2,000 lookups on the 1st regardless.
What you'd really like to know is whether this developer already had a free quota. Your tables only know accounts, and a new one has nothing tying it to the last.
How to protect your supplier bill and your paying customers
These hold up no matter who's behind the accounts. With the illustrative numbers above, each lookup goes like this:
Split your supplier cap. Keep 36 of the 40 lookups a second for paying keys and give free keys the other 4. The same 240,000 lookups now take 60,000 seconds, nearly 17 hours, and the month-end run never meets them. That answers the message at the top, though the bill stays the same.
Stop resetting everyone on the 1st. Reset each account on its own signup date, so no single minute carries the whole free tier.
Give free lookups their own monthly budget. Say $1,500, which buys 125,000 lookups, about twice the 60,000 your real free developers use. When it's gone, free keys get a clear quota error and paying keys carry on, even if real developers get that error too.
Serve most of the free quota from a sample set. Offer a fixed set of records your license lets you serve without a per-lookup charge, plus 100 live lookups. A fully used free account drops from $24 to $1.20 (100 × $0.012). Every account gets the same sample, so it doesn't add up to anything, and 240,000 live lookups would now take 2,400 accounts.
Put a bulk option on the quota error, if your license allows one. Some collectors would pay for a file.
Decide what a no looks like. Give consultants a way to ask for more, and say it plainly.
Evaluate each free quota before it goes out
Every step above limits what a quota can do once it exists. None of them looks at the claim for the quota, and you don't have to build the thing that does. That's the job AbuseZero was built for, and we'll happily brag about it.
Go back to the table. For the email rows, AbuseZero checks mailbox aliases, disposable domains and mail routing, and it recognizes repeat devices across new accounts, even when email addresses keep changing. For the IP and VPN rows, it sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. Then there's what no row comes near: multi-layer AI risk analysis that examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and a proprietary algorithm, with AI that checks the claim again. Creating a fresh account isn't enough to erase previous activity.
Your server makes one API call before a free quota goes live and gets a clear allow or deny, under rules you control. Eligibility can be once ever, once per calendar month or once every set number of days. Observe mode shows you what would be denied before anyone is blocked, and the quickstart protects your first benefit. Your app still issues keys and counts lookups, and you'll still want that split cap.
Frequently asked questions
Will rate limiting stop multiple accounts on a free API quota?
No. A rate limit stops bursts on one key, but 120 keys can each stay under it. See rate limiting vs abuse prevention.
Should I remove the free tier from my data API?
Keep that as a last resort. Developers test against real records before they buy, and removing the free tier takes that away.
What about the free accounts I already have?
Only reset accounts that come back and ask, so dormant ones cost nothing. If you use AbuseZero, you can import your claim history so earlier claims are on record.
Keep your free quota for developers who'll build on it
Start with Builder
Pay as you go. Protect your first free quota today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.