Payments and usageDiscuss an integration
Understand the usage consuming your free-credit budget.
Every free trial spends real compute. See which signups and runs come from repeated automated accounts, and connect that evidence to the limits, payment checks and reviews you already run.
For AI and SaaS teams offering free credits or costly operations.
Opens your email app, addressed to support@doubleagent.so.
See how it worksWhere $50,000 of free credits went
- SignupsSignups: 10,000
- Free credits grantedFree credits granted: $50,000
- Repeat-trial patternRepeat-trial pattern: 1,500
- Credit cost at stakeCredit cost at stake: $7,500
Human 80%Agent 2%Bot 13%Unknown 5%
Where money is affected
Free credits are paid for in compute.
Inference, extraction and search cost money per call. A script that opens trial after trial spends your budget without ever becoming a customer.
Automation alone is not the problem: your paying customers’ agents call your API all day. The question is which usage is eligible for free credits, and that is your policy.
The real picture
The trial funnel, two ways.
Illustrative example Hypothetical figures; your own numbers will differ.
Your numbers
What it could mean for you.
Replace the example with your own figures.
- Credit cost at stake
- $7,500
- Credit cost per real trial
- $5.88
- Accounts to review
- 1,500
At stake = signups × share repeat-trial × credit. Cost per real trial = credits granted ÷ trials not automated.
Illustrative example Your numbers, not a promise. Savings depend on the decisions you make with the evidence.
An example decision
Three accounts, three different answers.
- Paying customer’s agent
- Authorized: keep serving
- New trial, person at a browser
- Legitimate: grant credits
- Fifth trial from one script
- Suspected abuse: review
- Your control
- Payment check before credits
Same automation, different decisions. Your policy draws the line.
How it fits
From evidence to a decision.
- 01
Observe the signup
Label web signups and credit claims in the browser.
- 02
Authenticate API use
Use account and service-event evidence for API calls; a browser script does not see them.
- 03
Join metered usage
Connect accounts to the resource units they consume.
- 04
Apply your controls
Review, require payment, budget or rate-limit, as you decide.
What your team can do
Act on it, your way.
Hold credits for review
Delay free credits for suspected repeat trials.
Ask for a payment method
Require a card before costly operations.
Measure marginal cost
Track real resource cost, with estimates labelled.
Before you start.
Isn’t all API traffic automated?
Yes. Human versus bot is not the eligibility rule; repeated trial abuse is.
Does the browser script see my API calls?
No. Server calls need authenticated account and service evidence.
Is this a gateway or entitlement system?
No. It informs the controls you run; we do not promise a released gateway or cross-account identity detector.
How do I compare it with my rate limits?
Measure what it adds beyond the rate limiting already in place, after false positives.
Discuss an integration
See the real picture.
Opens your email app, addressed to support@doubleagent.so.