Location context
Use available IP-derived location fields to inform regional defaults. Keep a fallback when location is missing or uncertain.
Field referenceGEO · IP · USER-AGENT · RISK SIGNALS
The Intelligence API for Modern Applications
Add location, network, user-agent and supported risk signals to your application. Inspect the response, understand the fields and build your own decision logic.
Start with a sample. See what each field means before you integrate.
Enter an IP address and, where supported, a user-agent string. Review the returned data alongside its field definitions.
Signals provide context, not proof of identity or fraud. Unavailable data is shown explicitly.
Idle — load a sample or run a live lookup.
Hover a field name for its meaning.
Signals
Use available IP-derived location fields to inform regional defaults. Keep a fallback when location is missing or uncertain.
Field referenceInspect supported network fields to understand the infrastructure associated with an IP address.
Field referenceParse the supplied user-agent string into supported browser, operating-system and device categories — plus crawler and automation hints.
Field referenceReview available risk indicators alongside their definitions and limitations before deciding how your application should respond.
Field referenceUse cases
Suggest a region when location data is available, and let the user change it.
Explore localizationCombine supported risk signals with your own application events to decide when a signup needs another check.
Explore signup checksUse parsed user-agent information to investigate compatibility issues and improve support workflows.
Explore user-agent parsingIntegration
Start with a documented request. Keep credentials on your server, handle missing fields and test the failure cases before going live.
Transparency
Review field definitions, coverage notes and data-handling details before using a signal in production.
IP geolocation is an estimate. VPN/proxy flags are feed-based. Missing fields mean unavailable — not clean.
Coverage notesSend only the IP and optional context you already process. Demo lookups are rate-limited and separate from production keys.
Data handlingCheck the live health endpoint for readiness after deploys.
Service statusAn unavailable signal is not a clean result. Your application should handle uncertainty explicitly.
Pricing
Compare included usage, request limits and the fields available on each plan. Billable unit = one lookup.
Start here
€0/mo
€29/mo
€99/mo
Custom
Enter your work email to continue to Stripe Checkout.
FAQ
No. An IP address describes a network connection and may be shared by multiple people or devices.
No. Treat IP-derived location as an estimate. Keep user-controlled alternatives where location affects the experience.
No. Use supported signals as inputs to your own decision process, alongside relevant application context.
It means the response does not provide a usable value for that field. Check the field reference for handling guidance.
Use the documented request examples and integration brief. Keep API keys in server-side environment variables and review generated code before deployment.
See pricing for usage limits and the data-handling notes for processing details.
Get API access
Inspect a response, choose the signals you need and start with the quickstart. Free tier: 1,000 lookups/day, no card.
Inspect a response, choose the signals you need and start with the quickstart.