Ipregistry User-Agent Parsing

Use the Ipregistry User-Agent Parsing API to identify the browser or client, device, rendering engine, and operating system described by a supplied User-Agent string. Provide the complete string through the required ua query parameter so the returned information describes your input. Use the parsed fields to segment website analytics, adapt download instructions, or understand the clients appearing in application access logs. Results describe the string itself and do not independently verify a device or visitor identity. The detail page includes parameter guidance, a verified Firefox example, response fields, and per-call pricing.

Selected price
$0.000667 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Complete User-Agent string to parse. Required in this OpenAny profile so the result describes the supplied string.
Optional native response-field selector. Omit it to receive the full response. See https://ipregistry.co/docs/filtering.

Sample response

{
  "device": {
    "brand": null,
    "name": "Desktop",
    "type": "desktop"
  },
  "engine": {
    "name": "Gecko",
    "type": "browser",
    "version": "128.0",
    "version_major": "128"
  },
  "header": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0",
  "name": "Firefox",
  "os": {
    "name": "Windows NT",
    "type": "desktop",
    "version": ">=10"
  },
  "type": "browser",
  "version": "128.0",
  "version_major": "128"
}

Response result

Response structure

Inferred from examples
  • deviceobject
    • brandnull
    • namestring
    • typestring
  • engineobject
    • namestring
    • typestring
    • versionstring
    • version_majorstring
  • headerstring
  • namestring
  • osobject
    • namestring
    • typestring
    • versionstring
  • typestring
  • versionstring
  • version_majorstring

Loading related APIs…

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Ipregistry User-Agent Parsing with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.