GetClickInfo

GEO · IP · USER-AGENT · RISK SIGNALS

GetClickInfo

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.

Inspect a request. Explore the response.

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

Understand the signals your application receives.

Location context

Use available IP-derived location fields to inform regional defaults. Keep a fallback when location is missing or uncertain.

Field reference

Network context

Inspect supported network fields to understand the infrastructure associated with an IP address.

Field reference

User-agent context

Parse the supplied user-agent string into supported browser, operating-system and device categories — plus crawler and automation hints.

Field reference

Risk context

Review available risk indicators alongside their definitions and limitations before deciding how your application should respond.

Field reference

Use cases

Turn request context into application behavior.

Set useful regional defaults

Suggest a region when location data is available, and let the user change it.

Explore localization

Add context to signup review

Combine supported risk signals with your own application events to decide when a signup needs another check.

Explore signup checks

Understand client environments

Use parsed user-agent information to investigate compatibility issues and improve support workflows.

Explore user-agent parsing

Integration

A clear path from example to integration.

Start with a documented request. Keep credentials on your server, handle missing fields and test the failure cases before going live.

  1. Get API access
  2. Run a documented request
  3. Add your application rules

Open the API quickstart · Copy integration brief


        

Transparency

Know what the data can—and cannot—tell you.

Review field definitions, coverage notes and data-handling details before using a signal in production.

Coverage and limitations

IP geolocation is an estimate. VPN/proxy flags are feed-based. Missing fields mean unavailable — not clean.

Coverage notes

Data handling

Send only the IP and optional context you already process. Demo lookups are rate-limited and separate from production keys.

Data handling

Service health

Check the live health endpoint for readiness after deploys.

Service status

An unavailable signal is not a clean result. Your application should handle uncertainty explicitly.

Pricing

Know what each request costs.

Compare included usage, request limits and the fields available on each plan. Billable unit = one lookup.

Metered IP APIs Pay-per-lookup · costs spike with traffic
vs
GetClickInfo Flat daily limits · Free / Pro / Business

Pro

€29/mo

100,000 lookups / day · burst 200 / min · hard stop at limit

  • Everything in Free
  • Stripe billing portal
  • Same signals, higher quota
  • Cancel anytime in portal

Business

€99/mo

2,000,000 lookups / day · burst 1,000 / min · hard stop at limit

  • Everything in Pro
  • High-volume workloads
  • Same API contract
  • Cancel anytime in portal

Enterprise

Custom

Custom volume · VPC · procurement

  • Custom limits & support terms
  • Security questionnaires
  • Invoice-friendly path
  • Contracted cancellation terms
Contact sales

FAQ

Before you build.

Does an IP address identify a person?

No. An IP address describes a network connection and may be shared by multiple people or devices.

Is IP geolocation an exact location?

No. Treat IP-derived location as an estimate. Keep user-controlled alternatives where location affects the experience.

Does a VPN or proxy signal mean fraud?

No. Use supported signals as inputs to your own decision process, alongside relevant application context.

What does an unavailable field mean?

It means the response does not provide a usable value for that field. Check the field reference for handling guidance.

Can I use the API with an AI coding tool?

Use the documented request examples and integration brief. Keep API keys in server-side environment variables and review generated code before deployment.

Where can I find limits and data-handling details?

See pricing for usage limits and the data-handling notes for processing details.

Get API access

Build with better request context.

Inspect a response, choose the signals you need and start with the quickstart. Free tier: 1,000 lookups/day, no card.

  • API key shown once after signup
  • Account request builder for JS, Python, Go and more
  • Upgrade to Pro or Business when volume grows

Create Free account

Already have an account? Log in

Build with better request context.

Inspect a response, choose the signals you need and start with the quickstart.