Skip to content

IP Address Information Through One Scraping API

Pulling IP intelligence from public lookup pages usually means stitching together proxy rotation, a headless browser and a parser.

OUTPUT FORMATSHTMLJSONMarkdown

This page describes a managed single-call alternative: you send a URL, the service renders the page and handles anti-bot measures, and you receive either rendered HTML or structured JSON. The field list, request controls and credit rules below are the practical details to check before you commit.

What a single call returns

The service accepts a public IP-information or geolocation page URL and returns the rendered result. According to the product description, the fields that typically parse in one call across major IP-lookup services are: IP address, country, region, city, latitude/longitude, ISP, organization, timezone and ASN. You can request raw rendered HTML, or ask for structured JSON through extraction rules (CSS selectors) or AI-driven extraction. The same call handles proxy rotation and headless browser rendering, so you do not manage those components yourself.

Three common workflows

IP data tends to feed one of three jobs. First, geolocation enrichment: attaching country, region and city to leads or traffic so you can segment or position against competitors. Second, geo-based market segmentation: tailoring outreach or content by region. Third, ISP and network detail: identifying the provider or organization behind an address for security review or reliability checks. The field list above supports all three, but the output shape depends on whether you use extraction rules or AI extraction.

Request controls and when to use them

The advanced parameters are the levers that change cost and behavior. Use render_js when the target page builds its IP fields with JavaScript; the service runs the page in a real headless browser and returns post-render HTML. Use stealth_proxy when a target reacts aggressively to normal traffic. Use country_code to route requests through a specific geography. Use extract_rules for CSS-selector output or ai_extract_rules when you want natural-language extraction. Each of these has a credit implication, so match the control to the actual page behavior rather than enabling everything by default.

Credit cost map

The plan table below lists the reference tiers, monthly credit allowances and concurrency limits. For IP lookups, the credit rules that matter are: a base request starts at 1 credit; enabling JS rendering costs 5 credits per successful request; enabling premium proxies costs 10 credits with JS rendering off or 25 credits with it on. Credit validity is set by the operator's current terms. Plan prices are shown exclusive of VAT unless stated otherwise. Cancellation terms are governed by the operator's current policy. Treat the figures as a dated reference and confirm current pricing before purchase.

Build-vs-buy checklist

Before choosing a managed API over a self-built stack, confirm these items against your own requirements:

  • Proxy rotation: do you need residential or premium proxies, and at what request volume?
  • Headless rendering: do the target IP pages require JavaScript, and can you afford the 5-credit rendering cost per request?
  • Anti-bot handling: do the targets challenge normal traffic, and will you need stealth_proxy?
  • Structured output: do you want raw HTML, CSS-selector extraction, or AI extraction?
  • Concurrency: how many simultaneous requests does your pipeline send, and does the plan tier cover it?
  • Data fields: are country, region, city, lat/long, ISP, organization, timezone and ASN sufficient, or do you need additional fields?
  • Legal review: have you checked the target site's terms of service and avoided post-login content?

Worked example: from URL to JSON

Suppose you send a public IP-information page for a single address. With render_js enabled and ai_extract_rules set to request the standard field set, a realistic structured response would include the address itself, country, region, city, latitude/longitude, ISP, organization, timezone and ASN. If you instead use extract_rules with CSS selectors, you map each field to the selector on that specific page. If the page is static and you only need raw HTML, a base request at 1 credit is enough. The example is illustrative of the field list, not a guarantee of any particular page's layout.

Blocked vs. empty extraction

A blocked request and an empty extraction are different failures. A blocked request usually returns an error status or a challenge page; the fix is to enable stealth_proxy or adjust the request pattern. An empty extraction returns a successful response but missing fields; the fix is to check your CSS selectors or refine the AI extraction prompt. Conflating the two leads to wasted credits and misdiagnosis. If the page renders but fields are blank, start with the extraction rule, not the proxy.

Getting started

Create an account to receive an API key and any introductory credits the operator currently offers. Install one of the supplied SDKs (Python, Node.js, Go, PHP, Ruby or Java) or use raw cURL. Send a GET or POST request with the target URL. For a first test, start with a base request against a static IP-information page, confirm the fields you need, then add render_js or stealth_proxy only if the page requires them. The dashboard request builder can generate a code snippet in your preferred language if you prefer not to write the request by hand.

Plan reference (captured pricing)
PlanMonthly priceAPI creditsConcurrent requestsJS renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

Reference pricing; prices shown exclusive of VAT unless stated otherwise; credit validity is set by the operator's current terms. Confirm current pricing before purchase.

Frequently asked questions

Is scraping IP address data legal?

Public-facing pages are generally fair game for collection, but the target site's terms of service still govern what you may do. Read those terms before you deploy, and stay away from anything behind a login.

What data can I extract from IP address data?

Whatever the public page actually renders. To get structured JSON back, either map fields with extract_rules using CSS selectors, or let ai_extract_rules handle the extraction from a natural-language description.

How do I start scraping IP address data?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. Any introductory credits offered at sign-up can be used to test.

Will I get blocked when scraping IP address data?

Requests are routed through rotating residential proxies and a genuine headless browser, which makes them resemble ordinary visitor traffic. If a particular target starts pushing back hard, switch on stealth_proxy for that request.

Can I scrape IP address data without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.

How do I handle JavaScript when scraping IP address data?

Pass render_js=true on the request. The service runs the page in a real headless browser, executes the JS server-side, and returns the post-render HTML.

How many credits does an IP lookup consume?

A base request starts at 1 credit. Enabling JS rendering costs 5 credits per successful request. Enabling premium proxies costs 10 credits with JS rendering off or 25 credits with it on. Credit validity is set by the operator's current terms.