Typhoeus (Ruby/libcurl) user agent
Typhoeus is a Ruby HTTP client that wraps libcurl to make fast, parallel requests, often used for crawling and bulk API work. By default it sends a user agent that names the Typhoeus library unless the caller overrides it. That token marks a request as scripted Ruby traffic rather than a human browser.
What this means
Typhoeus is a Ruby library built on libcurl, designed to issue many HTTP requests in parallel efficiently. That makes it a common choice for crawlers, bulk API consumers, and integrations that need throughput.
When code does not set a custom user agent, Typhoeus sends a default that names the library with a version. This is distinct from Ruby's Net::HTTP or Faraday, which have their own defaults; a bare Typhoeus token points specifically at this client.
How it appears
Look for a Typhoeus product token with a version and no browser compatibility chain. The libcurl backing may also surface curl-related details depending on configuration, but the Typhoeus name is the distinguishing marker.
Because overriding the user agent is trivial, many production clients replace the default with an application string. Match the default to catch unconfigured clients, but do not assume its absence means no Typhoeus traffic.
- Ruby HTTP client built on libcurl for parallel requests
- Default user agent names the Typhoeus library
- Distinct from Net::HTTP and Faraday; easily overridden
How it appears in analytics and logs
A user agent naming Typhoeus indicates a Ruby program using the libcurl-backed Typhoeus client, often for parallel fetching. It is automation — an integration or scraper — not a human page view.
Diagnostic use case
Identify scripted Ruby traffic from Typhoeus by its library-named default, and recognise that the default is commonly replaced with a custom string.
What WebmasterID can help detect
WebmasterID classifies the Typhoeus default as scripted, non-browser traffic, helping keep parallel Ruby HTTP work separate from human analytics.
Common mistakes
- Assuming all Ruby HTTP traffic shows a Typhoeus token.
- Confusing Typhoeus with Faraday or Net::HTTP defaults.
- Counting Typhoeus parallel fetches as human page views.
Privacy and accuracy notes
The Typhoeus token identifies the HTTP library, not a person. WebmasterID reads it as a coarse automation signal only.
Related pages
- Ruby and Faraday user agents
Ruby applications make HTTP requests through the standard net/http library and popular wrappers like Faraday. These send library-style default user agents — for example a Ruby token from net/http or a Faraday token — that identify server-side Ruby automation rather than a human browser. Defaults are commonly customised.
- curl, wget and script user agents
Command-line and library HTTP clients send a default user agent that names the tool: curl/x.y, Wget, python-requests, Go-http-client, and similar. These are scripts, not browsers, and seeing them is normal. This page explains the patterns and how to treat them without over- or under-reacting.
- API client user agents (Postman, etc.)
Developers exercise APIs with tools like Postman, Insomnia, and HTTPie, each of which sends a recognisable default user agent (for example a PostmanRuntime token). Seeing these means someone is testing or scripting against your API, not browsing your pages. This page covers the patterns and how to read them.
- Bot intelligence
Surface libcurl-backed Ruby HTTP traffic separately from human visits.
Sources and verification notes
- Typhoeus — project READMERuby HTTP client built on libcurl; sends a Typhoeus-named default user agent unless overridden.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.