sseMITupdated 1mo ago
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.
¿Qué puedes hacer con User Agent Parser API?
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.003 | 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
Instalación
Añade User Agent Parser API a tu cliente. Elige el que uses.
claude mcp add --transport sse user-agent-parser-api https://user-agent-parser.api.klymax402.com/mcpcodex mcp add user-agent-parser-api --url https://user-agent-parser.api.klymax402.com/mcp{
"mcpServers": {
"user-agent-parser-api": {
"url": "https://user-agent-parser.api.klymax402.com/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"user-agent-parser-api": {
"type": "sse",
"url": "https://user-agent-parser.api.klymax402.com/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"user-agent-parser-api": {
"url": "https://user-agent-parser.api.klymax402.com/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"user-agent-parser-api": {
"serverUrl": "https://user-agent-parser.api.klymax402.com/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
1 herramienta
User Agent Parser API expone una herramienta a un agente conectado.
- utility_parse_user_agent
- POST
Puntuación
76 / 100
Buena
- Documentación22/25
- Mantenimiento25/25
- Confianza13/20
- Capacidad4/15
- Instalación12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 25 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 1 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Historial de versiones
| Versiones | Publicada |
|---|---|
| 1.1.0Última | 16 may 2026 |
| 1.0.2 | 23 abr 2026 |
| 1.0.1 | 13 abr 2026 |
| 1.0.0 | 13 abr 2026 |