Skip to main content
Glama
Br0ski777

user-agent-parser

by Br0ski777

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"
    }
  }
}

Related MCP server: Pylon MCP Server

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.

License

MIT

A
license - permissive license
Not graded
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • F
    license
    Not graded
    quality
    F
    maintenance
    20 pay-per-call utility tools for AI agents via x402 USDC micropayments on Base. Screenshots, OCR, PDF, web scraping, weather, forex rates, crypto/stock prices, DNS, geocoding, translation, and more. $0.001–$0.008 per call. No API keys, no signup.
    1
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to pay for x402 pay-per-use services like web search, scraping, and screenshots using a simple API key and USD balance, without managing crypto wallets.
    6
    MIT

View all related MCP servers

Related MCP Connectors

  • Pay-per-use weather, environment, finance, and on-chain intelligence tools for AI agents via x402.

  • Pay-per-call web scraping for AI agents via x402 on Base USDC. Six tools, no signup.

  • 63 pay-per-call tools for agents: vision, text, data, web, blockchain. USDC on Base via x402.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Br0ski777/user-agent-parser-x402'

If you have feedback or need assistance with the MCP directory API, please join our Discord server