User Agent Parser X402 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited User Agent Parser X402 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Parse any user agent string into structured data: browser, OS, device type, engine, and bot detection in one call. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"user-agent-parser": {
"url": "https://user-agent-parser.api.klymax402.com/mcp"
}
}
}curl -X POST "https://user-agent-parser.api.klymax402.com/api/parse" \
-H "Content-Type: application/json" \
-d '{"userAgent":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response bodyAny x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
utility_parse_user_agent | POST | /api/parse | $0.003 | Parse a user agent string into structured data |
utility_parse_user_agentUse this when you need to parse a user agent string to identify the client's browser, OS, device type, and bot status. Returns fully structured data.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
userAgent | string | yes | The user agent string to parse |
Example response:
{"browser":{"name":"Chrome","version":"120.0"},"os":{"name":"Windows","version":"11"},"device":{"type":"desktop","vendor":null,"model":null},"engine":"Blink","isBot":false,"botName":null}When to use: analytics pipelines that need to classify traffic by device or browser, detecting bot traffic in access logs, or adapting content based on client capabilities.
Not for: HTTP header analysis (use utility_parse_http_headers), web scraping (use web_scrape_to_markdown), SEO auditing (use seo_audit_page).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.