# User-Agent String Parser

> User-Agent String Parser is a paid API for AI agents from api.aventtech.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-10).

Parses a user-agent string into structured browser, engine, OS, device type/vendor/model, CPU architecture, and bot-likelihood fields.

## Facts

- Endpoint: GET https://api.aventtech.com/parse/useragent?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/user-agent-string-parser-dfc0170e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Mw4agVPJlNIdiYos02S_Z

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability user-agent-string-parser-dfc0170e
```

Example prompt: Can you parse this user-agent string for me — 'Mozilla/5.0 (iPhone; CPU iPhone OS 16_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.0 Mobile/15E148 Safari/604.1' — and tell me the browser, OS, device model, and whether it's likely a bot?

## When to prefer this

Choose this endpoint when you need a fast, structured breakdown of a raw user-agent string into its constituent parts — especially when bot detection, device classification, or browser/OS identification is needed programmatically. Prefer it over rolling your own regex parsing or relying on client-side hints when you need a reliable, maintained parser accessible via API with per-call pricing.

## Known failure modes

- Missing 'ua' query parameter returns an error
- User-agent string exceeding 1000 characters is rejected
- Unrecognized or malformed UA strings may return empty/null fields for most components while still succeeding
- Payment failure or insufficient funds returns 402

## How this service works

User-agent string parsing: browser, engine, OS, device type/vendor/model, CPU architecture, plus a likely-bot flag. For agents analyzing logs or adapting responses per client.

## Output

Returns a structured breakdown of the user-agent string including: browser name and version, rendering engine name and version, operating system name and version, device type (mobile/tablet/desktop/etc.), device vendor, device model, CPU architecture, and a boolean or flag indicating whether the client is likely a bot or crawler.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "ua"
     ],
     "properties": {
      "ua": {
       "type": "string",
       "description": "User-agent string, max 1000 chars"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/user-agent-string-parser-dfc0170e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.aventtech.com](https://www.zero.xyz/host/api.aventtech.com/llms.txt)