/ip-intelligence/ — Ipregistry
Get location, ASN and separate proxy, VPN, Tor and relay signals in every API plan. Choose credits for hosted lookups or separately licensed datasets for local processing.
IP intelligence. Official documentation · Checked · Review due .
Choose a product and access method
documented decisionSwipe or scroll the table to compare response checks and billing.
| Starting point | Access method | Check before use | Billing basis |
|---|---|---|---|
| You need occasional lookups without a subscription | Use a one-time credit pack after the signup credits. | Packs include the same response fields as subscriptions and do not expire. | The entry pack lists 15,000 credits for $10.[3] |
| You need to identify Tor exits specifically | Read security.is_tor_exit in the IP response. | security.is_tor also covers middle relays and bridges; it is a broader classification. | These fields are included across API plans.[1][3] |
| You want to enrich multiple addresses together | Use a batch endpoint and count the IP lookups in the request. | One HTTP request is not one credit for a batch. | Budget one credit per lookup plus one per batch request.[3] |
| You need local lookups on your own infrastructure | Choose the required downloadable datasets and formats. | Datasets are separate subscriptions; confirm redistribution rights if results will be supplied to customers. | Dataset prices cover internal use, with a custom redistribution license available.[2][3] |
documented capabilities
HTTP API- Delivery
- Hosted JSON API and separately subscribed CSV/MMDB datasets for local lookup. The AS dataset is listed as CSV only.[1][2]
- Location data
- Country, region, city, postal code and approximate coordinates. Unknown field values are null; coordinates do not identify a household or street address.[1]
- ASN and network
- ASN, announcing route, network name and type, company details and mobile-carrier fields are documented.[1]
- Privacy signals
- Separate proxy, residential-proxy, VPN, relay, Tor-relay, Tor-exit and cloud-provider flags. Every API plan includes the full response; these fields are not reserved for a higher API tier.[1][3]
- Access and free use
- An account and API key are required. New accounts receive 20,000 free credits once, without a stated time limit; this is not a recurring monthly allocation.[4][3]
- Billing unit
- A single lookup uses one credit. Batch endpoints use one credit per lookup plus one for the batch request. Monthly allowances and non-expiring packs are separate purchasing options.[3]
- IP versions
- IP lookup fields document both IPv4 and IPv6 addresses.[1]
- Tor and relay definitions
- is_tor includes Tor exit relays, middle relays and bridges. Use is_tor_exit for exits specifically. The separate is_relay field currently covers Apple Private Relay.[1]
- Offline licensing
- Published dataset prices cover private internal use. Redistributing data to customers requires a separate custom license.[3]
Billing: API subscriptions supply monthly credits; one-time credit packs do not expire. Single lookups cost one credit, while batches cost one per lookup plus one. Offline datasets have separate subscriptions.
Outputs: json, csv, mmdb
Documented for: Ipregistry IP Intelligence API, Ipregistry IP Datasets
getting started
documentation reviewed- Choose the hosted API or the specific local datasets needed for the application.
- For API use, create an account and obtain a key; send it in the key query parameter or Authorization: ApiKey header.
- Restrict keys by source IP, origin or configured usage limits where appropriate, and preserve null field values when parsing responses.
- For local processing, obtain the relevant dataset subscription and load its CSV or MMDB files with a compatible reader.
Requirements & limitations
- Company data can identify a shared network operator rather than the visitor's employer; the documentation gives a shared-office example.
- Tor-relay and Tor-exit flags have different scopes. The relay flag currently covers Apple Private Relay only.
- Signup credits are a one-time allocation. API credits do not establish access to every offline dataset.
- IP classifications and approximate coordinates do not establish an individual's location or intent.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
4 references- IP Address Response FieldsChecked 2026-10-01
- IP DatasetsChecked 2026-10-01
- Flexible PricingChecked 2026-10-01
- AuthenticationChecked 2026-10-01