IP geolocation APIs you can pay per call

What IP geolocation APIs do

An IP geolocation API turns a network address into geographic context. Depending on the documented output, that context can be a country, region, city, coordinates or timezone. An IP intelligence route can add network ownership, an autonomous system number, an ISP label or a risk assessment. These fields answer different questions. A country label describes an inferred location; an ASN describes network registration and routing context; a threat flag describes the provider's evidence about activity or infrastructure.

An agent might use location context to choose a language, summarize traffic by region or investigate an unexpected login. The input must be the address relevant to that decision. A lookup of the requesting machine can locate the agent's infrastructure rather than the person it is helping. A route that accepts an explicit IPv4 or IPv6 address provides a different input contract from one that examines its caller. Preserve that distinction in the integration rather than assuming a parameter can be added to either product.

A coordinate returned for an IP is not a device GPS reading or a verified street address. Shared egress, mobile networks, VPNs, proxies and hosting infrastructure can separate the network address from the location of a person. A precise-looking decimal does not establish a precise physical position. Let the application carry an uncertain or unavailable location without inventing a home, office or recipient address.

Risk information needs its own interpretation. A listed proxy, hosting network or blacklist match can be useful context without proving malicious intent. Keep the source, observation time and reason fields. A provider score should feed a documented review policy, particularly when blocking a request would affect a legitimate user.

Compare the returned data, scope and limitations

The location type includes endpoints that explicitly return geographic context for an IP. The network type covers ASN or ownership information. A combined profile can belong to both. Reverse DNS is a hostname lookup, not reverse geographic lookup: a PTR name does not establish the physical location of the device. Risk and batch-screening products stay separate from geographic quotes so that a cheaper blacklist check cannot supply a city's lookup price.

Subnet arithmetic, domain WHOIS, satellite imagery and address-to-coordinate geocoding are neighboring products. A subnet calculator works on CIDR notation without locating a person. A satellite product starts with coordinates rather than deriving them from an IP. Domain and URL assessments may use the hosting IP internally without returning the IP lookup product the caller needs. The task selection keeps the documented outputs rather than relying on a gateway's general description.

A provider-declared upstream identifies a named lookup source or threat feed when the endpoint explicitly advertises it. A source name is not a freshness or accuracy guarantee. Preserve the version or observation time returned by the actual request and distinguish a missing upstream signal from a negative result.

SuVerse Pay advertise ipwho.is in their matched endpoint descriptions. NetIntel name AbuseIPDB or AlienVault OTX in matched threat-reputation descriptions.

Each price is the cheapest endpoint of that service for that kind of data: the same number wherever this page quotes it.

Compare 6 IP geolocation services

Each row retains the selected task endpoint and its reference price. The ordering follows observed paying wallets for the service; it does not rank the accuracy of the underlying output.

$/CALL is the price of the endpoint named under it: the cheapest ip location: country, region, city or coordinates endpoint of the service or, for a service without one, its cheapest IP geolocation endpoint. Never the cheapest tool of a gateway. Other kinds of data have their own price in the tables below. IP GEOLOCATION ENDPOINTS counts the IP geolocation endpoints out of all the endpoints the service lists. BUYERS 30D counts distinct wallets that paid the whole service on-chain in 30 days, not only its IP geolocation endpoints. "Generalist" marks a gateway that sells more than three unrelated kinds of tools: it is never called the cheapest.

How to choose an IP geolocation endpoint

Match the network address to the decision

For a client-facing workflow, establish which address a trusted ingress supplies and how the provider accepts it. Avoid locating a reverse proxy by accident. Keep IPv4 and IPv6 behavior in the evaluation set, along with unsupported and private-address inputs. An unavailable location should remain unavailable; it should not silently become the provider's edge location.

Separate geography from an enforcement score

A fraud review can use location, ASN and reputation as separate evidence fields. Write the action rule before connecting a score to a block decision. Check whether the provider reports per-source failures and whether a combined verdict survives a missing component. Compare the explanation and time of observation with the needs of your workflow.

Write an acceptance criterion

Choose the fields your next step requires before choosing a provider. Keep a small reviewed input set with straightforward cases, ambiguous cases and expected failures. Compare the raw fields and reason codes with that criterion rather than accepting a successful HTTP status as a complete result.

Keep provenance with the result

Store the input, selected route, observation time and provider-specific identifiers together. Preserve a missing value independently from zero, false or an explicit negative verdict. This helps an agent decide whether to retry, request clarification or accept a partial result without silently inventing certainty.

Test the operating limits

The monitored median uptime is 100% and the median selected quote is $0.0025. Monitoring latency describes our checks, rather than a benchmark of your full paid workflow. Evaluate response size, timeout behavior and concurrency for a representative workload. Check whether a retry repeats a completed purchase and whether a later page or deeper product costs extra.

Choose by the output your workflow needs

Start with the response your next step can consume. The candidates below use the same type classification as the comparison table. The job quote belongs to the lowest priced endpoint of its requested types, with the originating path retained.

IP location: country, region, city or coordinates

Choose the IP that the route actually examines. Keep address family, geographic granularity and unknown results with the returned location.

Candidates today, most buyers first: NetIntel ($0.002/call, generalist, 100 buyers) · WebberSites x402 Data API ($0.001/call, generalist, 33 buyers) · SuVerse Pay ($0.05/call, generalist, 28 buyers) · IPIntel.ai IP Lookup & Risk API ($0.001/call, 25 buyers) · IPIntel.ai x402 Tools ($0.003/call, 25 buyers) · ip402.xyz ($0.01/call, 24 buyers)

ASN, ISP and network ownership

An ASN and an ISP or organization name describe who operates the address block, not who sits behind the address. Store the ASN number with the name and the lookup date.

Candidates today, most buyers first: NetIntel ($0.002/call, generalist, 100 buyers) · SuVerse Pay ($0.05/call, generalist, 28 buyers) · IPIntel.ai IP Lookup & Risk API ($0.001/call, 25 buyers) · IPIntel.ai x402 Tools ($0.003/call, 25 buyers) · ip402.xyz ($0.01/call, 24 buyers)

IP risk, reputation and blacklist evidence

Inspect the contributing signals and the meaning of unknown before mapping a provider score to your own allow, review or block policy.

Candidates today, most buyers first: NetIntel ($0.05/call, generalist, 100 buyers) · IPIntel.ai IP Lookup & Risk API ($0.001/call, 25 buyers)

Reverse DNS and PTR hostname data

A PTR hostname is published by whoever controls the reverse zone and can be missing. Record an empty answer separately from a failed lookup, and do not read a hostname as a verified owner.

Candidates today, most buyers first: IPIntel.ai IP Lookup & Risk API ($0.001/call, 25 buyers) · IPIntel.ai x402 Tools ($0.001/call, 25 buyers)

What the providers describe

These paragraphs attribute output contracts and limitations to the provider. Reference prices follow the matching endpoint type rather than an amount embedded in a marketing description.

NetIntel

NetIntel separates /ip-geo/locate, /asn-lookup/analyze, reputation and combined IP reports. The location quote starts at $0.002, while risk evidence starts at $0.05. Its location description advertises city, region, country, coordinates, timezone and ISP/ASN. The combined report advertises concurrent components with partial-failure handling. Choose the combined contract when the next step needs the linked evidence, and preserve unavailable components rather than flattening them into a clean verdict. A risk quote does not replace the geographic route's quote.

6 IP geolocation endpoints of 124 · $0.002/call (GET /ip-geo/locate) · Base/SOL · uptime 30d 100% · 107 ms · 100 buyers in 30 days

IPIntel.ai IP Lookup & Risk API

IPIntel's dedicated lookup listing describes /x402v2 as an IPv4 or IPv6 profile at $0.001. The advertised response combines location, ASN, ISP, organization and reverse DNS with risk labels, proxy or hosting signals and bot-related evidence. Those are the provider's advertised signals, not an independently confirmed location or threat determination. Store the geographic fields separately from the risk label so a later policy change can use the evidence without having to repeat the original inference.

1 IP geolocation endpoint of 1 · $0.001/call (POST /x402v2) · Base · uptime 30d 100% · 1075 ms · 25 buyers in 30 days

IPIntel.ai x402 Tools

The IPIntel tool package lists /ip-lookup at $0.003 and a separate PTR lookup starting at $0.001. Its IP description advertises location, ASN, ISP, organization, reverse DNS, timezone and proxy, mobile or hosting indicators. Satellite observations and domain-health checks have separate inputs and outputs, so their prices do not describe this IP request. An agent choosing this package should retain the selected tool and input address in the result record rather than treating the package as one interchangeable response.

2 IP geolocation endpoints of 10 · $0.003/call (POST /ip-lookup) · Base · uptime 30d 100% · 256 ms · 25 buyers in 30 days

SuVerse Pay

SuVerse describes /v1/data/ip-geolocation as a lookup of the requesting IP at $0.05. It advertises country, region, city, timezone, ISP and ASN. This input contract matters for a hosted agent: the requesting IP may belong to the runtime executing the call. The description does not establish that this captured route accepts an arbitrary target address. Check the current request schema before using it to enrich a user's connection record, and record whose network location the result actually represents.

1 IP geolocation endpoint of 10 · $0.05/call (GET /v1/data/ip-geolocation) · Base/SOL · uptime 30d 99.9% · 253 ms · 28 buyers in 30 days

Cost per call and for a larger workload

The median selected route costs $0.0025 per call. At the same input shape, 100,000 calls total $250.00. Use the generated table as a reference calculation, then measure how many requests produce one accepted result in your workflow.

Each service at the price of its main IP geolocation endpoint, the one named in the table above.

A request can inspect one input, return several records or buy a bounded batch. Those units are different. Follow-up lookups, pagination, retries and a larger input can change the amount required. Preserve the exact endpoint, submitted parameters, returned quote and outcome so that a cheap submission is not mistaken for a cheap completed task. A variable-price route needs its own request quote; a priced neighbor cannot establish its total.

Set an explicit budget for each job and a stopping condition for repeated attempts. Separate an invalid input, an empty answer and an unavailable upstream in the result record. The provider's terms determine whether those outcomes incur a charge. Read the challenge for the exact request before authorizing a payment, and avoid estimating a task from the gateway's cheapest unrelated utility.

Inspect a request and its payment evidence

For geographic output, NetIntel documents GET /ip-geo/locate, with a location reference quote of $0.002. Read its current schema to supply the intended IP and verify the response fields your workflow needs.

The listed method and description establish the advertised contract. This explanation does not reproduce an HTTP 402 challenge or certify a paid response. Open the service page's payment evidence and obtain the challenge for the exact request before authorizing payment. Compare resource, method, input, network, asset and amount together; do not reuse a challenge for a neighboring DNS or risk tool.

How this comparison is built

The comparison starts with services that are online and payment-ready, have a known price, a description of at least 80 characters and measured 30-day uptime of at least 90%. Task selection then inspects the documented endpoints. A phrase in the service description can identify a candidate without establishing that a captured route returns the desired output. Pages below the index threshold can still be read directly.

Provider output claims were reviewed against the public service and endpoint descriptions captured on October 22, 2026. They remain provider claims. Monitoring supplies operating figures and reference prices; it does not establish that a returned location matches the device or person behind an address. Buyer counts describe observed paying wallets for the service, with the coverage limits explained on its linked page.

The endpoint classification supplies the comparison quote, per-type prices and job candidates. A row requires a fixed quote for a documented IP-location output. Risk, network and reverse-DNS products remain adjacent types and cannot qualify a service without a location product. Keep the named path when comparing services: an adjacent product can have a different input, unit and evidentiary value even on the same host.

Questions

How to pay

Each service answers an unpaid call with HTTP 402 and its price; your agent signs a USDC payment on the listed network and retries. No API key, no account, no subscription. See what x402 is.