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...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
ipregistryCurrent Ipregistry User-Agent Parsing · GET · View API reference | $0.000667 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
deviceobjectbrandnullnamestringtypestring
engineobjectnamestringtypestringversionstringversion_majorstring
headerstringnamestringosobjectnamestringtypestringversionstring
typestringversionstringversion_majorstring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
device?: {
brand?: null;
name?: string;
type?: string;
};
engine?: {
name?: string;
type?: string;
version?: string;
version_major?: string;
};
header?: string;
name?: string;
os?: {
name?: string;
type?: string;
version?: string;
};
type?: string;
version?: string;
version_major?: string;
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/ipregistry/user-agent/parse- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/ipregistry/user-agent/parse?ua=Mozilla%2F5.0+%28Windows+NT+10.0%3B+Win64%3B+x64%3B+rv%3A128.0%29+Gecko%2F20100101+Firefox%2F128.0' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
ua | URL query parametersquery | string | Yes | Complete User-Agent string to parse. Required in this OpenAny profile so the result describes the supplied string. minLength: 1 |
fields | URL query parametersquery | string | No | Optional native response-field selector. Omit it to receive the full response. See https://ipregistry.co/docs/filtering. minLength: 1 |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Published documentation example. Verify the actual response after an approved call.
{
"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"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# 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.
## Available implementations
ipregistry · Ipregistry User-Agent Parsing: https://openany.si/markets/apis/capabilities/ipregistry-user-agent-parsing?offering=db79cc41-f7c7-483c-b68e-c0e41645e069 · $0.000667 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/ipregistry-user-agent-parsing
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/ipregistry/user-agent/parse
Price: $0.000667 / call
Provider: ipregistry
Contract revision: 1
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/ipregistry/user-agent/parse?ua=Mozilla%2F5.0+%28Windows+NT+10.0%3B+Win64%3B+x64%3B+rv%3A128.0%29+Gecko%2F20100101+Firefox%2F128.0' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "Ipregistry User-Agent Parsing",
"endpoint": "https://api.openany.si/v1/agent-apis/ipregistry/user-agent/parse",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Complete User-Agent string to parse. Required in this OpenAny profile so the result describes the supplied string.",
"location": "query",
"min_length": 1,
"name": "ua",
"nullable": false,
"required": true,
"type": "string"
},
{
"description": "Optional native response-field selector. Omit it to receive the full response. See https://ipregistry.co/docs/filtering.",
"location": "query",
"min_length": 1,
"name": "fields",
"nullable": false,
"required": false,
"type": "string"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "667",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Documentation example",
"request": {
"body": null,
"headers": {},
"path": {},
"query": {
"ua": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0"
}
},
"response_body": {
"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"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Documentation example
Published documentation example. Verify the actual response after an approved call.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 2
Review these request fields before running. Keep the published provider and request method unchanged.
ua- Complete User-Agent string to parse. Required in this OpenAny profile so the result describes the supplied string.
fields- Optional native response-field selector. Omit it to receive the full response. See https://ipregistry.co/docs/filtering.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/ipregistry/user-agent/parse?ua=Mozilla%2F5.0+%28Windows+NT+10.0%3B+Win64%3B+x64%3B+rv%3A128.0%29+Gecko%2F20100101+Firefox%2F128.0' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Documented HTTP 200
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" }
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.