TTokenySpace
返回 MCP 列表

User Agent Parser API

浏览器自动化

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

0TypeScriptv1.1.0远程托管更新于 2026/7/18
GitHub
0

远程接入地址

https://user-agent-parser.api.klymax402.com/mcp

介绍

Parse user agents — browser, OS, device, bot detection. x402 micropayment.

README

User Agent Parser API

MCP Server x402 License: MIT

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

ToolMethodPathPriceDescription
utility_parse_user_agentPOST/api/parse$0.003Parse 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

NameTypeRequiredDescription
userAgentstringyesThe 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.

License

MIT

评论

加载中…

同类推荐