workingproxysites.
[ new post ]
[ menu ]

directory

boards

[all]

information

/ip-intelligence/ — Abstract IP Geolocation API

Evaluate location and ASN enrichment, with company and security fields shown in higher-tier product examples. A free allowance supports evaluation; reconcile the public pricing and response-reference differences before committing to a paid integration.

IP intelligence. Official documentation · Checked · Review due .

Choose a product and access method

documented decision

Swipe or scroll the table to compare response checks and billing.

Starting pointAccess methodCheck before useBilling basis
You want to evaluate location and ASN fieldsStart with the free IP Geolocation allowance and its API-specific key.Check the response used by your account against the fields your application needs; the published schemas differ.The documented free allowance is 1,000 requests per month at 1 request per second.[1][3][2]
You need company information alongside locationEvaluate the Standard tier described in the product examples.Confirm the actual response contract and commercial terms before committing; v1 field paths are not interchangeable with the newer examples.Obtain the applicable paid quote; this comparison does not resolve the conflicting paid volumes and rate limits.[2][3][4]
You need separate VPN, proxy and Tor signalsEvaluate Professional's documented product example.Confirm separate flag availability and schema. The linked v1 reference only defines a combined VPN/proxy field.Paid usage is metered separately for this API and can incur overages or an automatic upgrade under the terms.[2][1][3][4]

documented capabilities

HTTP API
Delivery
The technical reference documents a key-authenticated HTTP API with JSON output. Its v1 schema differs from the current product-tier examples.[1][2]
Location data
Country, region, city, postal code, coordinates and timezone appear in the reference and product examples. Their nesting and field names differ between those sources.[1][2]
ASN and network
Current Starter examples include ASN fields; Standard adds company information. The v1 reference separately documents ASN, ISP, organization and connection type.[1][2]
Privacy signals
Current Professional examples show separate VPN, proxy, Tor, hosting and relay flags. The v1 reference defines security.is_vpn as VPN or proxy combined; confirm the schema supplied by the chosen plan.[1][2]
Access and free use
An IP Geolocation API key is required. Pricing documents 1,000 free monthly requests at 1 request per second, with no card. Free commercial-use permission is not explicit in the reviewed terms.[1][3][4]
Billing unit
Each API is billed separately by request subscription, with overage and possible automatic-upgrade terms. Public pages disagree on paid quotas and rate limits, so reconcile the applicable paid quote before purchase.[3][2][4]
IP versions
The v1 technical reference accepts both IPv4 and IPv6 in ip_address; omitting the parameter uses the caller's address.[1]
Free evaluation fields
The pricing FAQ says the free IP plan includes security and company fields. That statement does not resolve the differences between its current product examples and the linked v1 reference.[3][1][2]

Billing: Each Abstract API has its own request subscription. Free IP Geolocation documents 1,000 monthly requests at 1 request per second. Current paid quotas, rate limits and prices are not quoted here because the public pages disagree.

Outputs: json

Documented for: IP Geolocation API

[ official reference ][ JSON record ]

getting started

documentation reviewed
  1. Obtain a key for IP Geolocation; keys for other Abstract APIs are separate.
  2. Confirm the plan and response version before implementing field paths. The v1 reference documents api_key and an optional ip_address parameter.
  3. Keep unavailable location/network values distinct from negative detection results.
  4. Before paid use, reconcile the subscription quote, field contract, request allowance, per-second limit and overage behavior.

Requirements & limitations

  • Current product cards and the pricing FAQ disagree on paid quotas, per-second limits and effective prices. Exact paid figures are deliberately unlisted pending reconciliation.
  • The linked v1 reference and current tier examples use different response shapes. This record does not promise a single schema across them.
  • The Enterprise card mentions a commercial license, but that does not establish that other tiers prohibit business use; free commercial permission remains unclear from the reviewed sources.
  • Terms allow paid overages and automatic upgrades under stated volume or repeated rate-limit conditions. IP location and security labels are estimates/classifications, not proof about a person.

We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.

primary sources

4 references
  1. Abstract IP Geolocation API documentationChecked 2026-10-01
  2. Abstract IP Geolocation APIChecked 2026-10-01
  3. Abstract API PricingChecked 2026-10-01
  4. Abstract API Legal: Terms of UseChecked 2026-10-01

related listings