Parse user-agent strings into structured browser, OS, device, and CPU data via x402 micropayments.
What it does
AgentUtil UserAgent is an x402-enabled API that parses user-agent strings into structured components. The `/v1/parse` endpoint accepts a POST with a JSON body containing a `ua` field and returns detailed breakdowns of browser (name, version), rendering engine (name, version), operating system (name, version), device (type, vendor), and CPU architecture. The service also offers sibling endpoints at `/v1/detect` for bot/crawler detection with categorization and device-type classification, and `/v1/compare` for side-by-side browser compatibility analysis between two user-agent strings.
Pricing is listed in the OpenAPI spec as $0.001 per request in USDC on Base, with a free tier of 10 requests per day per IP requiring no signup. The OpenAPI spec is well-structured (v3.1.0) with full request and response schemas for all three endpoints.
Note: during probing, the `/v1/parse` endpoint returned HTTP 400 (not the expected 402 payment challenge) on a POST without a body, and 404 on GET. This may indicate the endpoint validates the request body before issuing a payment challenge, or the x402 gating may not be fully active. The service root at `https://useragent.agentutil.net` does respond (HTTP 200) with a simple UA Checker page, confirming the server is live. No separate documentation, pricing, or README pages were found beyond the OpenAPI spec.
Capabilities
Use cases
- —Parsing incoming user-agent headers to tailor content delivery in web applications
- —Detecting bots and crawlers to filter analytics or enforce access policies
- —Comparing two user-agent strings to assess browser compatibility for cross-browser testing
- —Enriching log data with structured browser, OS, and device metadata
- —Classifying traffic as desktop, mobile, tablet, bot, console, or smart TV
Fit
Best for
- —Autonomous agents needing structured UA data without maintaining a local parser
- —Bot detection as a lightweight API call
- —Quick browser compatibility checks between two user-agent strings
Not for
- —High-volume real-time UA parsing where a local library (e.g., ua-parser-js) would be cheaper
- —Full browser fingerprinting beyond the user-agent string
Quick start
curl -X POST https://useragent.agentutil.net/v1/parse \
-H 'Content-Type: application/json' \
-d '{"ua": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"}'Example
Request
{
"ua": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
}Response
{
"os": {
"name": "Windows",
"version": "10"
},
"cpu": {
"architecture": "amd64"
},
"raw": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36",
"device": {
"type": "desktop",
"vendor": ""
},
"engine": {
"name": "Blink",
"version": "125.0.0.0"
},
"browser": {
"name": "Chrome",
"version": "125.0.0.0"
}
}Endpoint
Quality
Full OpenAPI 3.1.0 schema with request/response definitions and pricing metadata is available, but the x402 payment challenge was not captured during probing (endpoint returned 400, not 402). No external docs or pricing pages exist. The response example is inferred from the schema, not observed.
Warnings
- —x402 challenge not confirmed: POST to /v1/parse returned HTTP 400, not the expected 402 payment challenge
- —No documentation, pricing, or README pages found beyond the OpenAPI spec
- —Response example is inferred from the OpenAPI schema, not from an actual API response
- —Free tier (10 req/day/IP) and paid pricing ($0.001/req USDC on Base) are stated only in the OpenAPI x-pricing extension and not independently verified
Citations
- —OpenAPI spec describes three endpoints: /v1/parse, /v1/detect, /v1/comparehttps://useragent.agentutil.net
- —Pricing is $0.001 per request in USDC on Base with a free tier of 10 requests/day/IPhttps://useragent.agentutil.net
- —Probe returned HTTP 400 on POST and 404 on GET for /v1/parsehttps://useragent.agentutil.net/v1/parse
- —Root page responds with HTTP 200 showing a UA Checker interfacehttps://useragent.agentutil.net