MiltenBot
Run by Milten
How to detect MiltenBot
MiltenBot signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from Milten; a copied user agent without the signature does not.
- Detection method
- SignedThe agent signs its requests, so its identity is verified cryptographically.
- Signals that identify it
- CryptographicA signed request verified cryptographically
- BehavioralAutomated clicks, typing and page flow instead of a person's
Every signal Verisoul checks for MiltenBot
MiltenBot signs its requests, so we verify who it is cryptographically, then check the rest of the session.
- Used
Cryptographic
A signed request verified cryptographically
- Not used
Network
Not needed to identify it
- Not used
Device
Not needed to identify it
- Used
Behavioral
Automated clicks, typing and page flow instead of a person's
How often you'll see it
Very uncommon
Rare, brand new, or not seen on Verisoul traffic yet
Questions about MiltenBot
How do you detect MiltenBot?
MiltenBot signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from Milten; a copied user agent without the signature does not.
What is MiltenBot?
MiltenBot is an AI agent from Milten that works in a browser and signs its requests.
Does MiltenBot identify itself?
Yes. MiltenBot signs its requests cryptographically, which is the strongest way an agent can identify itself.
Can a bot pretend to be MiltenBot?
Not convincingly. A bot can copy MiltenBot's user agent, but without Milten signing keys its requests fail verification and it is not labeled MiltenBot.
How common is MiltenBot?
Very uncommon. Rare, brand new, or not seen on Verisoul traffic yet.
What does the Verisoul API return for MiltenBot?
Every session Verisoul identifies as MiltenBot carries an agent block with id "miltenbot", name, provider, type "ai_agent", detection_method "signed" and the detection_signals used (cryptographic, behavioral). Build rules on the id, type and detection method.