AI free-tier abuse

Stop farming free credits on your AI product.

10 minutes

Every new account on an AI product costs real compute. Stop one person cycling accounts to run a business on your free tier.

What you will build: a check on the action you protect that allows normal users, asks doubtful ones to verify, and blocks the clear cases. See the ai free-tier abuse overview for the attack in pictures.

Before you start

Finish one Web quickstart (for example JavaScript or React) and one Server quickstart (for example Node.js). The decision code below is TypeScript; every server SDK returns the same event.

How the attack works

  • Credit cycling. A new account when the free credits run out.
  • Scripted sign-ups. Bots creating accounts to resell access.
  • API key farming. Many keys, one machine, pooled usage.

What to look at

FieldWhy it matters here
multiAccountAccounts per device, across browsers.
velocityMany accounts from one visitor in a day.
botAutomated sign-up scripts.
  1. 1

    Identify on the action

    Call the browser SDK when the user performs the action, not on page load, and send the eventId with the request. Pass your own user id as linkedId whenever you have one: the account signals count by it.

    TypeScript
    const { eventId } = await trace.get({ linkedId: user?.id, tags: { action: 'ai-free-tier-abuse' } });
  2. 2

    Verify on your server

    import { verifyEvent } from '@trace-id/sdk-node';
    
    const event = await verifyEvent(eventId, { secretKey: process.env.TRACE_SECRET_KEY!, endpoint, timeoutMs: 1500 }).catch(() => null);

    Events can be verified for 60 minutes. If verification fails, decide whether to fail open or closed; for most of this flow, fail open.

  3. 3

    Decide

    TypeScript
    const event = await trace.verify(eventId);
    
    if (event.signals.bot.detected) return block();
    const credits = event.signals.multiAccount.detected ? 0 : FREE_CREDITS;
    await createAccount(email, { credits, deviceId: event.deviceId });

    trace.verify() is the embedded call; with a server SDK, use the event from step 2 instead. The thresholds are yours. Trace scores and explains; event.reasons lists which signals added how much, so log it with every decision.

Example decisions

Free accounts from one device, illustrative:

AccountCredits usedDecisionWhy
[email protected]100 of 100AllowFirst free tier
[email protected]100 of 100AllowSecond account, under the limit
[email protected]newVerifymultiAccount: ask for a card
[email protected]newBlockmultiAccount + automatedInput

Roll it out

  1. Ship steps 1 to 3 with logging only: record the decision, block nothing.
  2. After a week, look at who would have been blocked or asked to verify. Shared computers, offices and privacy tools are the usual false positives.
  3. Turn on Verify first, then Block for the clearest cases.
Suggest an edit

Spotted something wrong or unclear? Tell us on GitHub and we will fix it.