How much does IP Lookup cost?

IP Lookup costs 3 sats per call.

The endpoint returns country, region, city, approximate location, latitude, longitude, Google Maps link, ISP, organization, and AS data for the requested IP address.

Is the map location exact?

No. The location is approximate GeoIP data and should be treated as city-level or regional guidance, not precise device location.

IP Lookup API • Live on Bitcoin mainnet

Look up IP geolocation and map-ready context in one call.

Use a funded session to resolve country, region, city, approximate location, coordinates, ISP, ASN, and a Google Maps link for a public IP address. Built for OSINT, enrichment, and quick operator lookups.

3 sats / call

POST /api/ip-lookup

Google Maps link included

What It Does

IP Lookup resolves GeoIP and ASN data into a response that is easier to use directly in dashboards, scripts, and investigations. Instead of just raw coordinates, it now returns an approximate_location string and a ready-to-open google_maps_url.

Returns country, region, city, and coordinates
Includes approximate_location for human-friendly output
Includes google_maps_url built from the returned coordinates
Also returns ISP, organization, and AS metadata

What To Expect

This endpoint uses local MMDB GeoIP databases. The results are useful for approximate location and operator context, but they are not exact device location data.

Best read as city-level or regional guidance
Useful for enrichment, triage, and map handoff
Good fit for agent workflows that need clickable location context
Current deployment is Bitcoin mainnet

Example Request

curl -X POST https://arkapi.dev/api/ip-lookup \
  -H "Authorization: Bearer ak_your_token" \
  -H "Content-Type: application/json" \
  -d '{"ip":"8.8.8.8"}' | jq

Use a funded token from the Fund page. The endpoint is also documented in /openapi.json for agents and service wrappers.

How To Call It

1. Open the Fund page and create a session.
2. Copy the bearer token from the session confirmation or dashboard.
3. Call POST /api/ip-lookup with that token in the Authorization header.

The landing page is public, but the lookup endpoint itself still requires a funded session token and a valid JSON body.

Example Body

{
  "ip": "8.8.8.8"
}

ip is required
Use a valid public IPv4 or IPv6 address

Example Response

{
  "success": true,
  "data": {
    "ip": "8.8.8.8",
    "country": "United States",
    "country_code": "US",
    "region": "Virginia",
    "city": "Ashburn",
    "approximate_location": "Ashburn, Virginia, United States",
    "lat": 39.0438,
    "lon": -77.4874,
    "google_maps_url": "https://www.google.com/maps?q=39.0438,-77.4874",
    "isp": "Google LLC",
    "org": "Google Public DNS",
    "as": "AS15169 Google LLC"
  },
  "cost_sats": 3,
  "balance_remaining": 1497,
  "response_ms": 7,
  "endpoint": "/api/ip-lookup"
}

Good Uses

Enrich logs and alerts with location and ASN context
Map suspicious or interesting IPs quickly without leaving your tooling
Give agents a cleaner handoff than raw coordinates alone
Support OSINT and incident triage workflows

If you also need reputation context, pair this with IP Abuse Check or use IP Intel for the combined response.

For broader platform usage, see the main docs and the live catalog.

Related APIs

IP Abuse Check adds AbuseIPDB reputation and report counts for the same IP.
IP Intel combines lookup, AbuseIPDB, RDAP abuse-desk data when published, and URLhaus host context.
Domain Intel is the better fit when you need nameserver, MX, TLS, WHOIS, and broader infrastructure context for a domain.