Turn a User-Agent into device, OS, browser, and bot answers, down to brand and model (SM-G998B becomes Samsung Galaxy S21 Ultra 5G). Bots come back named and categorized, AI crawlers included.
Bare GET /useragent parses the User-Agent that made the request. No key needed. Prefer the User-Agent request header. Forward Sec-CH-UA-* Client Hints when you have them. Modern Chrome freezes the UA string, and hints are how you get the real model and OS version back. Paid deep adds the full detail.
Parsing User-Agents since 2015. Over 400 million requests and 14 million distinct strings.
Bot & browser directory →Most parsed since 2015 →
Try it
$ curl "https://api.parseapi.com/useragent" \ -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" // 200 · ~17ms · USA { "useragent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36", "device": "desktop", "os": "macOS", "browser": "Chrome", "bot": false, "mobile": false }
Response fields
SPEED
Median time for a /useragent response to reach a real city, first byte back, measured live from 16 cities.
US
17ms
EU
26ms
APAC
45ms
LatAm
22ms
ME
127ms
Every number here comes from real requests to this API, 403 million of them, covering 14 million distinct strings, starting 2015. Not a survey, not a panel, the actual strings developers sent us.
Ranked by requests parsed across the whole archive. Every name is a page in the directory.
First sighting of each AI crawler in our traffic. A whole new species of visitor, practically overnight.