User Agent Parser X402

What is User Agent Parser X402?

User Agent Parser X402 is an MCP server that parses a user agent string into structured data—browser name and version, OS, device type, engine, and bot detection—in a single call. It operates on a pay-per-call basis via the x402 protocol (USDC on Base L2) with no signup, no API key, and no rate limits. It is part of the klymax402 marketplace offering 100 x402 micropayment APIs for AI agents.

How to use User Agent Parser X402?

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.

Key features of User Agent Parser X402

• 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.

Use cases of User Agent Parser X402

• Classify web traffic by device, browser, or OS in analytics pipelines.
• Detect bot traffic from user agent strings in access logs.
• Adapt content delivery based on client capabilities (e.g., mobile vs desktop).
• Enrich agent logs or auditing systems with structured user agent data.

FAQ from User Agent Parser X402

How does payment work for User Agent Parser X402?

The server uses the x402 protocol—a HTTP-native pay-per-call system. Each call costs $0.001 USDC on Base L2. No API key or account registration is required; the client handles the 402 → sign → retry cycle automatically if it is x402-aware.

What data does the parse tool return?

It returns browser (name, version), os (name, version), device (type, vendor, model), engine, and isBot boolean plus botName if applicable. Example output: {"browser":{"name":"Chrome","version":"120.0"},"os":{"name":"Windows","version":"11"},"device":{"type":"desktop","vendor":null,"model":null},"engine":"Blink","isBot":false,"botName":null}.

What dependencies or client software are required?

No server-side dependencies beyond an x402‑aware HTTP client. For MCP use, any standard MCP client works with the provided endpoint URL. For direct HTTP calls, you need a client that understands the x402 payment challenge (e.g., @x402/fetch, x402-agent-tools, or ATXP). The server itself has no runtime requirements beyond being accessible over the internet.

What are the limits of this tool compared to alternatives?

The README specifies that this parser is not for HTTP header analysis (use utility_parse_http_headers), web scraping (use web_scrape_to_markdown), or SEO auditing (use seo_audit_page). It is focused solely on parsing a single user agent string, not on extracting data from surrounding headers or pages.