User Agent Parser X402
About
Parse any user agent string into structured data: browser, OS, device type, engine, and bot detection in one call. -- x402 micropayment API + MCP server for AI agents
Details
- Author
- Br0ski777
- Downloads
- 245
- Categories
- AI
Jump to
- Parse any user agent string into structured data in one call.
- Returns browser, OS, device type, engine, and bot status.
- Pay-per-call via x402 (USDC on Base L2) — no API key or signup.
- No rate-limit walls; usage is transparent and per‑call.
- Part of the klymax402 marketplace with 100+ similar APIs.
- Supports both MCP and direct HTTP (x402) transports.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
User Agent Parser X402Command (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Add the server to your MCP client configuration (e.g., Claude Desktop, Cursor, ElizaOS) by including the URL https://user-agent-parser.api.klymax402.com/mcp in the mcpServers object. Alternatively, use the HTTP endpoint POST /api/parse with a JSON body containing the userAgent string; the response initially returns a 402 Payment Required with an x402 payment challenge, which any x402-aware client (such as @x402/fetch or x402-agent-tools) handles automatically. The available tool is utility_parse_user_agent.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"user agent parser x402": {
"user-agent-parser": {
"url": "https://user-agent-parser-production.up.railway.app/mcp",
"transport": "sse"
}
}
}
}McpServers
{
"user-agent-parser": {
"url": "https://user-agent-parser-production.up.railway.app/mcp",
"transport": "sse"
}
}User Agent Parser API
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.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"user-agent-parser": {
"url": "https://user-agent-parser.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
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 body
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
| utility_parse_user_agent | POST | /api/parse | $0.001 | Parse a user agent string into structured data |
utility_parse_user_agent
Use 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).
Example agent prompts
- "Parse a user agent string to identify the client's browser, OS, device type, and bot status"
Payment
- Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
- Network: Base L2 (eip155:8453)
- Asset: USDC
- Facilitator: Coinbase CDP (primary), PayAI (fallback)
- Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)
Part of klymax402
100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
