Yes. The Free tier is 600 requests a month at 100 requests a minute, across every endpoint in the catalog, with no credit card. Nothing about it expires.

What happens when I hit the quota?

Requests return 429 with the limit, what you have used, and which window you tripped — nothing is queued, and nothing is charged. The monthly quota resets on the 1st (UTC). There is no rollover: unused requests do not carry into the next month.

Do failed requests use up my quota?

A 5xx does not. If a source breaks on our side, the request is excluded from your monthly count. A 4xx does count — a wrong parameter is still a request we answered. Per-minute throttling counts everything, so a retry loop is still throttled.

Which tier do I need?

Start on Free. Every response carries the remaining quota in its headers, and the dashboard reads the same number enforcement uses, so you will see the ceiling coming rather than discovering it.

How is Zapi different from RapidAPI or Apify?

Zapi focuses on a consistent REST contract — one API key, one response format, one error pattern for every source. No need to learn per-provider quirks like on traditional marketplaces, and no need to set up scraping workflows like on Apify.

What about the legality of accessing public data?

Zapi only accesses data that is publicly available without a login. Responsibility for how it is ultimately used stays with the developer — make sure your use case complies with the original source's ToS and the regulations in your operating region.

Is there an official SDK?

One: zpi-sdk, for TypeScript and JavaScript. It carries a typed error hierarchy, retries only what is safe to retry, submits bulk jobs, and verifies webhook signatures. Everything else is plain REST — cURL or any HTTP client works.

Can I request a source that isn't in the catalog yet?

Yes, through the community Discord, on any tier.

Why are Pro and Ultra marked Soon?

Checkout is not open yet. The limits and features listed on those tiers are already built and enforced — what is pending is billing, not the product.

IP Geolocation

IP geolocation lookup — country, region, city, ISP, ASN, koordinat untuk IPv4 dan IPv6.

Endpoints: 1
Requests: 10
Updated: 3 months ago
For LLMs: llms.txt

Endpoint health19 hours ago

lookuppassing, 0.1s

1/1 passingdaily 01:00 WIB

Playground

1 endpoint

GET/v1/dev-tools:ip-geo/lookup5m cache1 paramchecking key…

Parameters

Response

EXAMPLE

{
  "ip": "8.8.8.8",
  "asn": "AS15169 Google LLC",
  "isp": "Google LLC",
  "org": "Google Public DNS",
  "zip": "20149",
  "city": "Ashburn",
  "region": "VA",
  "source": "geo",
  "country": "United States",
  "latitude": 39.03,
  "timezone": "America/New_York",
  "longitude": -77.5,
  "regionName": "Virginia",
  "countryCode": "US"
}

Code examples

Lookup

zpi-sdkrecommended

// npm i zpi-sdk
import { ZpiClient } from "zpi-sdk";

const client = new ZpiClient({ apiKey: "zpi_xxxxxxxxxxxxxxxxxxxxxxxx" });

const data = await client.run("dev-tools:ip-geo", "lookup", {
  "ip": "8.8.8.8"
});
console.log(data);

Full SDK reference →

cURL

request.sh

curl -X GET "https://api.zpi.web.id/v1/dev-tools:ip-geo/lookup?ip=8.8.8.8" \
  -H "x-api-key: zpi_xxxxxxxxxxxxxxxxxxxxxxxx"

Full reference

1 endpoint · plain text

GETLookup/v1/dev-tools:ip-geo/lookupPerform lookup dengan input yang diberikan.

Parameters

ipstringrequired: IP address (IPv4 atau IPv6)

Request

curl -X GET "https://api.zpi.web.id/v1/dev-tools:ip-geo/lookup?ip=8.8.8.8" \
  -H "x-api-key: zpi_xxxxxxxxxxxxxxxxxxxxxxxx"

Example response

{
  "ip": "8.8.8.8",
  "asn": "AS15169 Google LLC",
  "isp": "Google LLC",
  "org": "Google Public DNS",
  "zip": "20149",
  "city": "Ashburn",
  "region": "VA",
  "source": "geo",
  "country": "United States",
  "latitude": 39.03,
  "timezone": "America/New_York",
  "longitude": -77.5,
  "regionName": "Virginia",
  "countryCode": "US"
}

IP Geolocation

IP geolocation lookup — country, region, city, ISP, ASN, koordinat untuk IPv4 dan IPv6.

Endpoints: 1
Requests: 10
Updated: 3 months ago
For LLMs: llms.txt

Endpoint health19 hours ago

lookuppassing, 0.1s

1/1 passingdaily 01:00 WIB

Playground

1 endpoint

GET/v1/dev-tools:ip-geo/lookup5m cache1 paramchecking key…

Parameters

Response

EXAMPLE

{
  "ip": "8.8.8.8",
  "asn": "AS15169 Google LLC",
  "isp": "Google LLC",
  "org": "Google Public DNS",
  "zip": "20149",
  "city": "Ashburn",
  "region": "VA",
  "source": "geo",
  "country": "United States",
  "latitude": 39.03,
  "timezone": "America/New_York",
  "longitude": -77.5,
  "regionName": "Virginia",
  "countryCode": "US"
}

Code examples

Lookup

zpi-sdkrecommended

// npm i zpi-sdk
import { ZpiClient } from "zpi-sdk";

const client = new ZpiClient({ apiKey: "zpi_xxxxxxxxxxxxxxxxxxxxxxxx" });

const data = await client.run("dev-tools:ip-geo", "lookup", {
  "ip": "8.8.8.8"
});
console.log(data);

Full SDK reference →

cURL

request.sh

curl -X GET "https://api.zpi.web.id/v1/dev-tools:ip-geo/lookup?ip=8.8.8.8" \
  -H "x-api-key: zpi_xxxxxxxxxxxxxxxxxxxxxxxx"

Full reference

1 endpoint · plain text

GETLookup/v1/dev-tools:ip-geo/lookupPerform lookup dengan input yang diberikan.

Parameters

ipstringrequired: IP address (IPv4 atau IPv6)

Request

curl -X GET "https://api.zpi.web.id/v1/dev-tools:ip-geo/lookup?ip=8.8.8.8" \
  -H "x-api-key: zpi_xxxxxxxxxxxxxxxxxxxxxxxx"

Example response

{
  "ip": "8.8.8.8",
  "asn": "AS15169 Google LLC",
  "isp": "Google LLC",
  "org": "Google Public DNS",
  "zip": "20149",
  "city": "Ashburn",
  "region": "VA",
  "source": "geo",
  "country": "United States",
  "latitude": 39.03,
  "timezone": "America/New_York",
  "longitude": -77.5,
  "regionName": "Virginia",
  "countryCode": "US"
}

Playground

Code examples

Full reference

Parameters

Request

Example response

Related APIs

CF Sitekey Extractor

DNS Lookup

WHOIS Lookup

Meta/OG Preview

SSL Labs

HTTP Headers Inspector

Playground

Code examples

Full reference

Parameters

Request

Example response

Related APIs

CF Sitekey Extractor

DNS Lookup

WHOIS Lookup

Meta/OG Preview

SSL Labs

HTTP Headers Inspector