The bot-to-human spectrum: beyond binary bot detection
In short. The bot-to-human spectrum places an account on a continuum from clearly automated to clearly human, rather than assigning a binary bot-or-not label. It exists because real inauthentic activity is not binary: most consequential accounts are neither pure bots nor ordinary users but sit somewhere in between - semi-automated, human-assisted, or genuinely human but coordinated. A spectrum reflects how these accounts actually behave; a yes/no label distorts it.
Why binary bot detection fails
The instinct to ask “is this account a bot, yes or no” feels natural and is almost always wrong, because the interesting accounts refuse to sit at either end.
- Semi-automated and cyborg accounts mix scheduled automation with human posting. A binary tool has to force them to one pole, and either answer is misleading.
- Human-operated coordinated accounts are the ones that matter most in an influence operation - and they are, correctly, human-paced. A binary bot detector clears them, because on the automation question alone they look like ordinary people.
- Real, intense humans - an angry customer, an activist, a superfan - post at volume and can trip crude bot heuristics. Labelling them “bot” is the false-positive class that destroyed the credibility of earlier academic detectors.
A binary verdict has to collapse all of that into one bit of information, and the collapse is where the errors live. A spectrum keeps the information.
What the spectrum measures
A bot-to-human score is a behavioural measure. It reads how an account acts - the tempo and regularity of its activity, the degree of automation in its timing, the shape of its behaviour over time - rather than what it posts. Because it is behavioural, it is language-agnostic and far harder to fake than content: an operator can rewrite every post for free, but changing the underlying behavioural tempo of an account is costly.
The output is a position on the continuum - a discrete behavioural band, not a calibrated probability - and the engine computes a plain measure of how confident it is in that position, withholding a firm verdict when the evidence behind it is too thin. A score built on three data points should never be mistaken for one built on a rich history. (For why that confidence measure matters as much as the score itself, see calibrated confidence.)
How to read a spectrum score - and the second instrument
A spectrum score answers one question well: how automated is this account. It does not, on its own, answer a second, equally important question: is this account part of a coordinated operation.
That is a different measurement, made by a different instrument - coordination detection, which reads how accounts act together rather than how fast one account acts. The two must be read side by side. An account can sit mid-spectrum on automation - “mixed signals” - and still be a coordinated, inauthentic node in a bot network. Bot score is the automation lens; coordination is the inauthenticity lens. A middling automation score with a coordination flag is not unremarkable; it is a finding. Any honest reading crosses the two.
This is how PulseCheck is built: it scores every account on the bot-to-human spectrum, and reads that score alongside coordination signals rather than as a standalone verdict. For plain-language definitions of the spectrum and the related terms, see the glossary.
Frequently Asked Questions
What is the bot-to-human spectrum?
A scoring model that places an account on a continuum from clearly automated to clearly human, rather than a binary bot-or-not label, reflecting how real inauthentic activity actually behaves.
Why not just label an account a bot or not?
Because the most consequential accounts - semi-automated, human-assisted, or human-but-coordinated - sit between the poles. A binary label forces a distortion and produces both misses and false positives.
Is a mid-spectrum account safe?
Not necessarily. A human-paced account can still be part of a coordinated operation. The automation score must be read alongside coordination detection - two instruments, not one.
Is the score behavioural or content-based?
Behavioural. It reads how an account acts, which makes it language-agnostic and resistant to AI-generated content.