---
title: "IPGeolocation.io Free Plan: What's Included and What Isn't"
slug: "/help/whats-in-the-free-plan"
description: "IPGeolocation.io's Free plan costs $0, with 1,000 API credits a day, no credit card, and no overage fees. See what's included and what needs a paid plan."
---

# Is the IPGeolocation.io Free Plan Really Free?

By [Sheharyar Malik](https://www.linkedin.com/in/sheharyar-malik-haniel/) Senior Software Engineer

Posted on October 24, 2026 | 10 min read

![Is the IPGeolocation.io Free Plan Really Free?](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/is-the-ipgeolocation-free-plan-really-free-feature.png)

The IPGeolocation.io Free plan is really free: it costs $0, needs no credit card, and gives you 1,000 API credits a day for life. It also can't run up a bill. The Free plan has no overage, so once the day's credits are used, the API refuses further credit-consuming requests with HTTP 429 Too Many Requests until the allowance resets at 00:00 UTC. You can use it in production and for commercial purposes, and its lookup results come from the same database as paid plans.

The limits are on daily volume and on the data a Free key can request:

| Feature | IPGeolocation.io Free Plan |
| --- | --- |
| Price | $0, free for life |
| Credit card | Not required |
| Daily allowance | 1,000 API credits, reset at 00:00 UTC |
| Cost per call | 1 credit for an IP lookup or a Time Zone, User Agent (GET), or Astronomy API call |
| Rate limits | None per second or per minute |
| When credits run out | HTTP 429 Too Many Requests until the reset; no overage charges |
| Included data | Location, country metadata, currency, basic ASN, and time zone data; User-Agent header parsing |
| Needs a paid plan | Security data (VPN, proxy, and Tor detection), company and abuse contact data, bulk lookups, and user agent data inside the IP lookup, among others |
| Production and commercial use | Allowed within 1,000 credits a day |

To start, [create a free IPGeolocation.io account](https://app.ipgeolocation.io/signup).

* * *

## What the Free Plan Includes

An IPGeolocation.io Free plan key covers two kinds of calls at 1 credit each: IP lookups that return five groups of data, and three standalone APIs for time zones, user agent parsing, and astronomy.

An IP lookup returns:

*   **Location:** continent, country, state or province, district, city, ZIP code, latitude and longitude, whether the country is in the EU, and its flag.
*   **Country metadata:** calling code, country top-level domain, and the languages spoken.
*   **Currency:** the local currency's code, name, and symbol.
*   **ASN basics:** the AS number, the organization that operates it, and its registration country.
*   **Time zone:** the IANA zone name, UTC offset, current local time, and daylight saving details.

A Free IP lookup doesn't return user agent data. On the Free plan, that comes from a separate call to the User Agent API, so IP and user agent data for one visitor take two calls and 2 credits, and 1,000 daily credits cover 500 visitors that way. The standalone APIs a Free key can call:

*   [**Time Zone API**](https://ipgeolocation.io/timezone-api.html)**:** the time zone and current local time for a time zone name, coordinates, an address, an IP address, or an airport code, plus conversion between time zones.
*   [**User Agent API**](https://ipgeolocation.io/user-agent-api.html)**:** the browser, device, operating system, and layout engine, parsed from the User-Agent header of each GET request it receives at `/v3/user-agent`, with classifications for recognized crawlers and malformed or suspicious user-agent strings. Sending a custom string in a POST body, or parsing in bulk through `/v3/user-agent-bulk`, needs a paid plan.
*   [**Astronomy API**](https://ipgeolocation.io/astronomy-api.html)**:** sunrise, sunset, moonrise, moonset, and sun and moon positions for a location and date.

Credits are the unit IPGeolocation.io's API plans count usage in, and only successful (HTTP 200) responses use them.

The illustration below shows a free-key response structure.

![IPGeolocation.io Free-plan JSON response mapped to its location, country metadata, currency, basic ASN, and time-zone objects, with their available fields.](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/free-plan-response-format-and-objects-1.svg)

Here is a real request with a Free plan key, made for 165.227.0.0 on October 25, 2026. The data updates daily, so the same IP can show a different city on another day.

```bash
curl -i 'https://api.ipgeolocation.io/v3/ipgeo?apiKey=API_KEY&ip=165.227.0.0'
```

```json
HTTP/2 200 
content-type: application/json
vary: Origin
vary: Access-Control-Request-Method
vary: Access-Control-Request-Headers
x-credits-charged: 1

{
  "ip": "165.227.0.0",
  "location": {
    "continent_code": "NA",
    "continent_name": "North America",
    "country_code2": "US",
    "country_code3": "USA",
    "country_name": "United States",
    "country_name_official": "United States of America",
    "country_capital": "Washington, D.C.",
    "state_prov": "California",
    "state_code": "US-CA",
    "district": "Santa Clara County",
    "city": "Santa Clara",
    "zipcode": "95051",
    "latitude": "37.35983",
    "longitude": "-121.98144",
    "is_eu": false,
    "country_flag": "https://ipgeolocation.io/static/flags/us_64.png",
    "geoname_id": "5346804",
    "country_emoji": "🇺🇸"
  },
  "country_metadata": {
    "calling_code": "+1",
    "tld": ".us",
    "languages": [
      "en-US",
      "es-US",
      "haw",
      "fr"
    ]
  },
  "currency": {
    "code": "USD",
    "name": "US Dollar",
    "symbol": "$"
  },
  "asn": {
    "as_number": "AS14061",
    "organization": "DigitalOcean, LLC",
    "country": "US"
  },
  "time_zone": {
    "name": "America/Los_Angeles",
    "offset": -8,
    "offset_with_dst": -7,
    "current_time": "2026-10-25 00:11:17.130-0700",
    "current_time_unix": 1792912277.13,
    "current_tz_abbreviation": "PDT",
    "current_tz_full_name": "Pacific Daylight Time",
    "standard_tz_abbreviation": "PST",
    "standard_tz_full_name": "Pacific Standard Time",
    "is_dst": true,
    "dst_savings": 1,
    "dst_exists": true,
    "dst_tz_abbreviation": "PDT",
    "dst_tz_full_name": "Pacific Daylight Time",
    "dst_start": {
      "utc_time": "2026-03-08 TIME 10:00",
      "duration": "+1.00H",
      "gap": true,
      "date_time_after": "2026-03-08 TIME 03:00",
      "date_time_before": "2026-03-08 TIME 02:00",
      "overlap": false
    },
    "dst_end": {
      "utc_time": "2026-11-01 TIME 09:00",
      "duration": "-1.00H",
      "gap": false,
      "date_time_after": "2026-11-01 TIME 01:00",
      "date_time_before": "2026-11-01 TIME 02:00",
      "overlap": true
    }
  }
}
```

The `X-Credits-Charged: 1` header shows the call used 1 credit, and nothing paid is in the response: no `security`, `company`, `abuse`, `network`, or `user_agent` object, no extended ASN fields. Every endpoint is served over HTTPS, and on IP lookups the `fields` and `excludes` parameters trim the response to what you need. One endpoint doesn't need the plan at all: Get IP (`/v3/getip`) returns your public IP address, needs no API key, and uses no credits. The [field reference for the IP Geolocation API](https://ipgeolocation.io/documentation/ip-location-api.html) marks every field FREE or PAID.

* * *

## Paid-Only Data and Features

IPGeolocation.io's paid plans add the following data and features:

*   **Location precision:** accuracy radius, confidence, locality, and DMA code.
*   **Security data:** VPN, proxy, residential proxy, and Tor detection with a threat score from 0 to 100, plus bot, known-attacker, and spam flags.
*   **ASN and network details:** the ASN's type, domain, allocation date, and registry, plus the network route, connection type, and hostname.
*   **Company data:** the name, type, and domain of the company behind the address.
*   **Abuse contact data:** the registered contact for reporting abuse from the address.
*   **User agent parsing beyond the GET endpoint:** user agent data inside the IP lookup, plus custom-string (POST) and bulk parsing on the User Agent API.
*   **Delivery features:** bulk lookups, lookups by domain, responses in languages other than English, Request Origin (CORS) authentication, and extra API keys.
*   **Dedicated paid APIs:** the IP Security, ASN, and IP Abuse Contact APIs, plus Real-Time Proxy & VPN Detection, a browser-side script that tests a visitor's connection live instead of looking the address up.

Free plan API keys can't access paid data or paid endpoints. The API returns a 401 Unauthorized when the key requests a paid object or field through `include` (`include=security`, `include=abuse`, or `include=user_agent`, for example), sends the User Agent API a custom string in a POST body, calls the IP Security, ASN or IP Abuse Contact API, calls a bulk endpoint, looks up a domain, or asks for a language other than English. A 401 isn't a successful response, so it uses no credits.

![Free-plan request flowchart: HTTP 200 uses 1 credit, HTTP 401 rejects paid-only features without charging credits, and HTTP 429 indicates the daily allowance is exhausted.](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/free-plan-request-outcomes-200-401-429.svg)

If you call the API from a web page, one more limit matters. Request Origin (CORS) authentication, which lets a browser call the API without exposing your key, is a paid feature, so on the Free plan the key belongs on your server. The [tutorial on securing your API key](https://ipgeolocation.io/tutorials/secure-api-key-before-production) shows how to route browser calls through a backend. For the User Agent API, the backend call needs one extra step. The GET endpoint parses the User-Agent header of the request it receives, and the [User Agent API documentation](https://ipgeolocation.io/documentation/user-agent-api.html) describes it as meant for client-side calls, where the browser adds the visitor's header automatically. When your server makes the call instead, set that header to the visitor's user agent string, as the documentation's curl examples do.

For the full side-by-side, see [the pricing page's plan comparison](https://ipgeolocation.io/pricing.html).

* * *

## The 1,000-Credit Daily Limit

The IPGeolocation.io Free plan has a hard limit of 1,000 credits a day, with no per-second or per-minute rate limit on top of it. The allowance is shared: IP lookups and calls to the Time Zone, User Agent, and Astronomy APIs all draw from the same 1,000. Once the credits are used, the API answers further credit-consuming requests with HTTP 429 Too Many Requests until the allowance resets at 00:00 UTC. The 429 response says your plan's limit has been reached and suggests upgrading.

The Free plan does not offer paid overages. After you use the daily allowance, you can wait for the reset at 00:00 UTC or upgrade to a paid plan for more usage. Unused daily credits do not carry forward.

![Timeline showing IPGeolocation.io’s 1,000 daily Free-plan credits decreasing to zero, followed by HTTP 429 responses until the allowance resets at 00:00 UTC.](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/free-plan-daily-allowance-reset-00-00-utc.svg)

Your dashboard shows credits used and remaining, and every successful response carries an `X-Credits-Charged` header with what that call cost. To make the allowance go further, cache results per IP address and per user agent string, so repeat visitors don't cost a credit each time. And filter out private and reserved (bogon) addresses before calling: the API answers them with HTTP 423 and a message such as "'10.0.0.1' is a bogon IP address". Those calls use no credits but still cost a round trip.

* * *

## Who the Free Plan Is For

You can use the IPGeolocation.io Free plan in production and for commercial purposes, as long as you stay within 1,000 credits a day. The [Terms of Service](https://ipgeolocation.io/tos.html) allow production and commercial use on the Free Plan under the same license terms as a standard API subscription. Lookup results come from the same database on every plan, so the data a Free key gets is as accurate as on a paid plan. If you need more than 1,000 credits a day, upgrade to any paid plan without changing your code.

Sign up with a real company or personal email address, since signups from disposable addresses are deleted. IPGeolocation.io doesn't encourage opening extra Free accounts to multiply the daily allowance; if one account's 1,000 credits aren't enough, that's the point to look at a paid plan.

* * *

## When to Move to a Paid Plan

Move to a paid plan when any of these is true:

*   Your app regularly runs out of credits before 00:00 UTC.
*   A decision depends on [VPN, proxy, and Tor detection](https://ipgeolocation.io/ip-security-api.html) or a threat score.
*   You need company or abuse contact data for the addresses you see.
*   You need user agent data in bulk or in the same response as the IP data.
*   You have a batch of addresses to enrich at once.
*   Your web pages need to call the API directly without putting your key in the page.

IPGeolocation.io's paid plans start with Starter at $19 a month for 150,000 credits. Every paid tier includes the same features; the tiers differ in included credits, overage pricing, overage caps, and the number of extra API keys or Request Origins.

One paid [IP Geolocation API](https://ipgeolocation.io/ip-location-api.html) lookup can return location, security, ASN, company, abuse contact, time zone, and user agent data together, so a single response can show that a login from the expected city is coming through a VPN on a hosting network. That full lookup uses 4 credits rather than 1, because security data adds 2 and abuse contact data adds 1, while user agent data adds none. The [credits documentation](https://ipgeolocation.io/documentation/credits-usage.html) lists what each call costs.

Free trials of paid plans are available on request: [contact the IPGeolocation.io team for a trial](https://ipgeolocation.io/contact.html) to test paid data before you choose a plan.

## Frequently Asked Questions

### Can I use the IPGeolocation.io Free plan in production or for commercial use?

**Answer:** Yes. You can use the IPGeolocation.io Free plan in production and for commercial purposes, as long as you stay within 1,000 credits a day and follow the Terms of Service. Call the API from your server to keep your key private, because Request Origin (CORS) for browser calls is a paid feature.

### Is the IPGeolocation.io Free plan less accurate than paid plans?

**Answer:** No. Every plan, including the Free plan, gets its lookup results from the same database, so the data a Free key gets is as accurate as on a paid plan. For the same IP, the fields both plans return have the same values. Paid plans add more data, such as accuracy radius, company, network, and security data.

### What if I need more than 1,000 credits a day?

**Answer:** Upgrade to any paid plan from your account. Endpoints and response format are the same on every plan, so your code does not change. Starter costs $19 a month for 150,000 credits, and every paid tier includes the same data; the tiers differ in included credits, overage pricing and caps, and the number of extra API keys or Request Origins.

### Does the IPGeolocation.io Free plan expire?

**Answer:** No. The IPGeolocation.io Free plan is free for life: it's "Forever free," with 1,000 API credits a day and no end date.

### Do I need a credit card for the Free plan?

**Answer:** No. IPGeolocation.io doesn't ask for a payment method when you create a Free plan account; an email address or a Google or GitHub account is enough. Payment details come in when you buy a paid plan.

### What are the IPGeolocation.io free tier limits?

**Answer:** The IPGeolocation.io Free plan includes 1,000 API credits a day, shared across IP lookups and the Time Zone, User Agent, and Astronomy APIs, with no per-second or per-minute rate limits. Once the credits are used, further credit-consuming requests return HTTP 429 until the reset at 00:00 UTC, with no overage charges. Security, company, extended ASN and abuse contact data, bulk lookups, and POST user agent parsing need a paid plan.

### Is the User Agent API included in the IPGeolocation.io Free plan?

**Answer:** Yes, through its GET endpoint. On the IPGeolocation.io Free plan, the [User Agent API](https://ipgeolocation.io/user-agent-api.html) parses the User-Agent header of each GET request it receives for 1 credit, and returns the browser, device, operating system, and layout engine details. When your server makes the call, set that header to your visitor's user agent string. Custom strings sent in a POST body, bulk parsing, and user agent data inside the IP lookup need a paid plan.

### Can I call the Free plan API from the browser?

**Answer:** Only by exposing your key. Calling the IPGeolocation.io API straight from a web page puts your Free plan key in the page's code. [Request Origin (CORS) authentication](https://ipgeolocation.io/documentation/api-authentication.html) avoids that, but it's a paid feature. Keep the key on your server and call the API from there; for the User Agent API, set the request's User-Agent header to the visitor's user agent string.

### Is the IP geolocation database included in the Free plan?

**Answer:** No. The IPGeolocation.io Free plan covers the API only. The downloadable IP databases are a separate paid product with its own [database pricing](https://ipgeolocation.io/db-pricing.html).

### Can I try paid data such as VPN detection before paying?

**Answer:** Yes. IPGeolocation.io offers free trials of paid plans on request, so you can test paid data before choosing a plan. To check a single address right away, use the lookup box on the IP Security API page; it shows the address's threat score and VPN, proxy, and Tor flags in the browser, with no code required.

* * *

## Get a Free API Key

[Create a free IPGeolocation.io account](https://app.ipgeolocation.io/signup) to get 1,000 API credits a day for IP lookups with location, currency, basic ASN, and time zone data, plus User-Agent header parsing. When your app needs security, company, or abuse contact data, [see the paid plans](https://ipgeolocation.io/pricing.html).

### Related Help Articles

[![Can IPGeolocation.io Return Place Names in Other Languages?](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/visual-0-feature-globe-horizon.webp)](https://ipgeolocation.io/help/ip-geolocation-response-languages)

[Can IPGeolocation.io Return Place Names in Other Languages?](https://ipgeolocation.io/help/ip-geolocation-response-languages)

IPGeolocation.io returns continent, country, state, and city names in 13 languages on paid API plans, and its location databases carry 12. Here are the codes, the fields that change, and the errors to expect.

Posted on November 2, 2026

By [Abdullah Afzal](https://www.linkedin.com/in/abdullah-a-08ba162b7?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=android_app)

[Read More](https://ipgeolocation.io/help/ip-geolocation-response-languages)

[![What Is IPGeolocation.io? Key Facts on Its Products, Data, and Plans](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/11/ipgeolocation-io-key-facts-feature-h-orbit.png)](https://ipgeolocation.io/help/key-facts)

[What Is IPGeolocation.io? Key Facts on Its Products, Data, and Plans](https://ipgeolocation.io/help/key-facts)

IPGeolocation.io turns public IPv4 and IPv6 addresses into location, security, network, and company data through APIs, databases, and Snowflake. Here are the facts on each product, how the data is delivered, and how plans and credits work.

Posted on November 1, 2026

By [Sheharyar Malik](https://www.linkedin.com/in/sheharyar-malik-haniel/)

[Read More](https://ipgeolocation.io/help/key-facts)

[![Which IPGeolocation.io Product Should I Use?](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/which-ipgeolocation-product-should-i-use.png)](https://ipgeolocation.io/help/which-ipgeolocation-io-product-should-i-use)

[Which IPGeolocation.io Product Should I Use?](https://ipgeolocation.io/help/which-ipgeolocation-io-product-should-i-use)

Match your job to the right IPGeolocation.io product. One IP Geolocation API call covers most jobs; here is when a dedicated API, real-time VPN detection, or a database fits better.

Posted on October 30, 2026

By Abdul Mateen

[Read More](https://ipgeolocation.io/help/which-ipgeolocation-io-product-should-i-use)

[![Does IPGeolocation.io Store the IP Addresses You Look Up?](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/does-ipgeolocation-io-store-ip-addresses.png)](https://ipgeolocation.io/help/does-ipgeolocation-io-store-ip-addresses)

[Does IPGeolocation.io Store the IP Addresses You Look Up?](https://ipgeolocation.io/help/does-ipgeolocation-io-store-ip-addresses)

IPGeolocation.io keeps standard API access logs, including the IP addresses you look up, for 14 days and then deletes them. Here is what a log line holds, what we never do with it, and how to look up IP data without sending IPs at all.

Posted on October 29, 2026

By [Daud Ahmad](https://www.linkedin.com/in/daudahmad0303)

[Read More](https://ipgeolocation.io/help/does-ipgeolocation-io-store-ip-addresses)

[![Does IPGeolocation.io Offer Annual and Multi-Year Contracts?](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/visual-0-feature-contract-2c-three-terms-fanned.webp)](https://ipgeolocation.io/help/ipgeolocation-io-annual-and-multi-year-contracts)

[Does IPGeolocation.io Offer Annual and Multi-Year Contracts?](https://ipgeolocation.io/help/ipgeolocation-io-annual-and-multi-year-contracts)

Annual billing on IPGeolocation.io API plans gives you two months free, Enterprise API contracts can run for up to three years, and database contracts run one to three. Here's what each term changes, from credits to renewal.

Posted on October 28, 2026

By [Abdullah Afzal](https://www.linkedin.com/in/abdullah-a-08ba162b7?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=android_app)

[Read More](https://ipgeolocation.io/help/ipgeolocation-io-annual-and-multi-year-contracts)

[![How Does IPGeolocation.io Database Licensing Work?](https://blogs.ipgeolocation.io/blogs-site/content/images/2026/10/visual-0-feature-option-d-where-data-goes-1.webp)](https://ipgeolocation.io/help/how-ipgeolocation-io-database-licensing-works)

[How Does IPGeolocation.io Database Licensing Work?](https://ipgeolocation.io/help/how-ipgeolocation-io-database-licensing-works)

IPGeolocation.io database licensing comes down to where the files run, whether the use is internal or customer-facing, and how many servers run them. Here are the six license types, how servers are counted, and what the term covers.

Posted on October 25, 2026

By [Abdullah Afzal](https://www.linkedin.com/in/abdullah-a-08ba162b7?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=android_app)

[Read More](https://ipgeolocation.io/help/how-ipgeolocation-io-database-licensing-works)
