Use case / API & trial abuse
API & trial abuse
Not every request has a browser. For APIs and trials, Volance scores the evidence your edge already has and returns it to your server — no fabricated browser signals.
The problem
API endpoints and free trials get farmed: credential stuffing, bulk scraping through keys, and repeated signups to reset a trial. When there is no page to instrument, browser-based tools have little to go on, and a hard rate limit punishes good clients.
How Volance helps
Use a server-side-only integration. You send the request-level evidence your edge already sees — IP, header order, proxy headers, whether a cookie came back, and any signed agent disclosure — and Volance scores it without pretending a browser was present. Omit a field and the matching checks simply do not run.
What you see
- A score and verdict for each request, returned to your own backend.
- Which checks ran and what they read, for requests with no browser at all.
- Request evidence alongside session evidence, in one portal view.
Volance scores a session on human-likeness and returns the evidence. It is not a CAPTCHA and does not prove a human is present; enforcement stays on your server.
Frequently asked
Does Volance need a browser script for API scoring?
No. A server-only integration scores request-level evidence. Browser behavioural signals are additive where you have a page; they are never invented.
How is this different from rate limiting?
Rate limiting counts requests; Volance assesses them. Scores can distinguish a burst of legitimate automation from abuse, so your policy is not limited to a fixed threshold.
MAKE THE NEXT REQUEST MAKE SENSE.
Start where
it matters.
One script on your site.
One API call from your server.
Every signal behind the verdict, in your own portal.