Back to Blog

How to stop free minutes abuse in an AI transcription app

One person can push a whole archive through your free minutes. What free transcription minutes abuse costs, which basic fixes break and what to do next.

Last March you typed "Your first 120 minutes are free, every month" onto your pricing page, because a minute of audio cost you about two cents and two cents didn't seem worth arguing about.

Stay with this scenario, and swap in your own numbers as you go. It's the 1st of November, your free minutes have just reset, and at 9:30 a.m. your job queue holds 2,400 recordings of about an hour each. Your busiest day until now was 200. You open a few and the file names stop you: ep_0212_final.mp3 and ep_0213_final.mp3 in one free account, ep_0214_final.mp3 and ep_0215_final.mp3 in the next one, under a different email. Two episodes per account, because two hours is exactly what you give away.

That's free transcription minutes abuse, and from your dashboard it looks like people using your product. Someone has an archive to get through, and the line you wrote in March is paying for it. Here's what each minute costs, using assumptions you should replace:

Speech to text         $0.010 a minute
Speaker labels         $0.004
Summary and chapters   $0.005
Storage and delivery   $0.001
Total                  $0.020 a minute, or $1.20 an hour

Now say one archive is 1,800 hours of old episodes:

  • 1,800 hours × 60 = 108,000 minutes
  • 108,000 ÷ 120 free minutes = 900 free allowances
  • 300 accounts × 3 monthly resets = 900 free allowances
  • 108,000 × $0.02 = $2,160 in provider charges

Say four of these archives are running at once, on 300 accounts each. That's 1,200 accounts sending two files apiece, which is your 2,400 recordings: 144,000 minutes, or $2,880 of work sitting in the queue. You have 320 customers at $24, so $7,680 comes in each month. Your normal audio totals 172,000 minutes, or $3,440, and you've been keeping $4,240. This month the bill is $6,320, and you keep $1,360.

In this illustrative chart, the bars are your provider bill and the line is your revenue. The archives arrive in month 4.

Provider bill vs revenue, illustrative010002000300040005000600070008000123456US dollarsMonth
Provider bill vs revenue, illustrative02000400060008000123456US dollarsMonth

Your provider will charge your card for every one of those minutes, and free minutes bring in nothing, so this is cash leaving with no revenue behind it. Three resets get through all four archives, for $8,640 (3 × $2,880). That's more than a month of revenue. If you spend $12,000 a month on everything, it's about 22 days of runway ($8,640 ÷ $12,000 × 30). Close all 1,200 accounts tonight and the money stays spent, because the transcripts are already downloaded.

Your paying customers feel it before the invoice does. You run 40 jobs at once and an hour of audio takes 6 minutes, so 2,400 files is a 360-minute line (2,400 × 6 ÷ 40). At 10:05 a.m., a customer on your $24 plan uploads a 40-minute client interview. It usually comes back in 4 minutes. Today it arrives around 3:35 p.m., well after their 1 p.m. deadline. By evening, 15 customers want this month refunded, another $360, and you're facing a choice you never wanted: shrink the free plan that brought you most of those 320 customers, or pay for all of this again on the 1st of December.

Why free transcription minutes are so easy to farm

A transcript is finished work. Once the text is downloaded, the account that produced it is worth nothing to whoever opened it. That's the difference from most credit farming, where people at least have to keep using the app to get the value.

Archives make it worse, because an archive is one job with an end. Someone with 1,800 hours of audio wants it done once, so a subscription was never an obvious fit, and your monthly reset pays each account again without anyone asking.

The obvious fix is to cut the free minutes. Go from 120 to 30 and a 45-minute meeting no longer fits, so a new user can't finish a single recording to see if your transcripts are any good. The archive just needs four times the accounts, 4,800 instead of 1,200. Your honest users lose the plan, and the limit you pick decides how many extra accounts it invites.

Protect your cash and your queue first

These won't stop anyone from claiming, but they cap what a bad month costs.

Measure the audio yourself. Read the real length from the file on your server, after upload and before anything billable runs. Never rely on a number sent by the browser.

Reserve minutes before the job starts. Take them from a ledger in one transaction, and give them back if the job fails.

Give free audio its own lane. Keep 10 of your 40 slots for free jobs and the same 2,400 files take 24 hours (2,400 × 6 ÷ 10 = 1,440 minutes). Your customer's interview comes back in 4 minutes.

Set a hard cap on free spend. Real free use costs $1,200 a month in this scenario (60,000 × $0.02), so a $1,500 cap leaves $300 for anything else.

Run the extras on demand. Create the summary when someone opens the transcript. An archive nobody reads saves you $540 (108,000 × $0.005).

Reset each account on its own date, and only when it comes back. A reset on the 1st hands every account its minutes on the same morning.

[Not enough left]alt[Minutes available]Uploads a 58-minute fileReads the real lengthReserve 58 minutesReservedAdd the jobTranscript readyRefusedOffer a paid planUploaderYour appMinutes ledgerFree laneUploaderYour appMinutes ledgerFree lane
[Not enough left]alt[Minutes available]Uploadsa58-minutefileReadsthereallengthReserve 58minutesReservedAdd the jobTranscript readyRefusedOffer apaidplanUploaderYourappMinutesledgerFreelaneUploaderYourappMinutesledgerFreelane

Now look at what the cap does on a morning like this one. $1,500 buys 75,000 minutes, or 1,250 of those 2,400 files. If the files land together, 10 slots work through those 1,250 in 750 minutes (1,250 × 6 ÷ 10). The free lane is out of money by about 10 p.m. on the 1st, and the real free user who finds you on the 10th gets an error. The archive got its minutes first. A cap protects your bank account, and it treats every claim the same.

The basic fixes, and how each one breaks

What you'd like to know is whether the person behind account 301 has already had their 120 minutes. The basics can only answer smaller questions than that, though each one does catch something. Email is the easiest place to see the limit. A unique-email rule compares strings, and one inbox can have many: Gmail ignores dots, so pod.archive@gmail.com and podarchive@gmail.com are the same mailbox, and plus-tagged mail like podarchive+nov@gmail.com reaches that inbox too. There's more in how aliases create duplicate accounts.

FixWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead addressesAny second inbox that worksPeople whose code lands in spamDeliverability work
Unique emailsThe same address twiceEvery different addressAlmost nobodyVery little
Disposable-domain blocksKnown throwaway servicesNew domains and ordinary mailboxesPeople using privacy forwardingA list someone updates forever
Gmail dots and plus addressingOne inbox written several waysA second real mailboxA family sharing one inboxUpkeep as mail services change
CAPTCHASimple scriptsSomeone uploading by handPeople using screen readers or privacy toolsFees and lost signups
Phone requirementCasual second accountsAnyone with another numberFreelancers abroad without a reliable mobile numberA charge for every text
Card requirementCasual second accountsAnyone with another cardA student with one interview to transcribeFewer signups
One per IP addressRepeat signups on one connectionAny other networkNewsrooms, universities and householdsExceptions and tickets
VPN blocksKnown VPN rangesEverything off your listReporters and researchers who work behind oneAnother list to maintain
Rate limitsBursts from one account300 accounts sending two files eachSomeone uploading a whole conferenceTuning per route
Usage caps per accountOne account overrunningEach new account's fresh 120 minutesAnyone whose file runs past the capDeciding what happens to half a recording

Manual review has its own problem in this product. At one minute per account, 1,200 accounts is 20 hours, due again after every reset. It also means staff going through file names and transcripts of interviews, medical dictation and private calls, so read what your privacy policy promises before anyone starts.

Add every row above and your signup form puts a puzzle, a text message and a card in front of someone who wanted to try one recording. Each list and exception needs an owner from then on, and the real people you turn away don't file a ticket to tell you.

Evaluate each claim before the minutes go out

You don't have to build your own abuse prevention system to get this right. AbuseZero gives you one API call before free minutes are granted, and a clear allow or deny back, under rules you control. Your email rules could only judge the address in front of them, while AbuseZero's multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss. There's a proprietary algorithm here, with AI that checks the claim again. You don't have to maintain any of that by hand, since it checks mailbox aliases, disposable domains and mail routing. It sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence, which a one-per-IP rule never could. It recognizes repeat devices across new accounts, even when email addresses keep changing, and creating a fresh account isn't enough to erase previous activity.

Your eligibility rule can match your plan, such as once per calendar month for a monthly allowance. Observe mode shows you what would be denied before anyone is blocked. Your app still measures the audio, runs the queue and enforces the caps above. The quickstart protects your first benefit.

Frequently asked questions

How much does a free transcription minute really cost?

Add up speech to text, speaker labels, summaries, storage and delivery per audio minute. This post assumes $0.02. Work out your own number and multiply it by your free allowance.

How many free transcription minutes should I give away?

At least enough to finish one typical recording in your product. If the allowance is shorter than a normal upload, new users never see a result.

Is every second account abuse?

No. A freelancer might keep client work apart from personal recordings. Decide what you mean to give each user, then test it. AbuseZero's evaluations can run in Observe mode first, so you see the effect before anyone is denied.

Keep your free minutes for people trying your product

Keep reading

Copying your prompt…

Copied the to your clipboard. Give it to your coding agent & it will handle the rest.