IP Intel API • Live on Bitcoin mainnet

Combine IP context and abuse reputation in one call.

Use a funded session to resolve geolocation, ASN context, best-effort abuse-desk RDAP contact data when the registry publishes an abuse role, approximate location, Google Maps link, AbuseIPDB reputation, and URLhaus host context for a public IP address in one response.

6 sats / call
POST /api/ip-intel
GeoIP + RDAP + AbuseIPDB + URLhaus

What It Does

IP Intel combines the signals you usually want together: where an IP appears to be, whether it has been reported for abuse, whether the registry publishes an abuse-desk contact point for reporting, and whether URLhaus has seen malware-linked host activity on that IP. It also adds deterministic enrichment that is useful in practice, including reverse DNS, normalized network type, an ASN number, and a simple risk label.

  • Returns country, region, city, coordinates, and ASN context
  • Adds reverse DNS, network_type, and asn_number
  • Adds best-effort abuse_contact data from public RDAP when an abuse-role contact is published
  • Includes approximate_location and a google_maps_url
  • Includes AbuseIPDB score, report counts, last reported time, URLhaus host summary, and a deterministic risk verdict
  • Good fit for triage, enrichment, and recon workflows

Why It Helps

IP Lookup gives you location and ASN context. IP Abuse Check gives you reported abuse context. IP Intel is the combined version when you want both, plus a best-effort abuse-desk contact when published and a lightweight URLhaus host summary, without extra client logic.

  • Useful in incident review and alert enrichment
  • Good for pentest and OSINT workflows
  • Cheaper and simpler than stitching two responses in the client
  • Current deployment is Bitcoin mainnet

Example Request

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

Use a funded token from the Fund page. The endpoint is also documented in /openapi.json.

How To Call It

Example Body

{ "ip": "8.8.8.8", "max_age_days": 30 }
  • ip is required
  • max_age_days is optional and defaults to 30

Example Response

{ "success": true, "data": { "lookup": { "ip": "8.8.8.8", "country": "United States", "country_code": "US", "region": "California", "city": "Mountain View", "approximate_location": "Mountain View, California, United States", "lat": 37.422, "lon": -122.085, "google_maps_url": "https://www.google.com/maps?q=37.4220,-122.0850", "isp": "Google LLC", "org": "Google LLC", "as": "AS15169 Google LLC" }, "ip": "8.8.8.8", "reverse_dns": [ "dns.google" ], "asn_number": 15169, "network_type": "cdn", "reported_recently": true, "risk_label": "low", "risk_reason": "Provider is whitelisted and has no abuse score despite historical reports", "abuse": { "ip": "8.8.8.8", "abuse_confidence_score": 0, "country_code": "US", "usage_type": "Content Delivery Network", "isp": "Google LLC", "domain": "google.com", "total_reports": 25, "num_distinct_users": 19, "is_whitelisted": true, "source": "AbuseIPDB", "max_age_days": 30 }, "urlhaus_host": { "listed": false, "source": "URLhaus" }, "abuse_contact": { "name": "Abuse", "org": "Abuse", "email": "[email protected]", "phone": "+1-650-253-0000", "roles": ["abuse"], "source": "ARIN RDAP", "is_abuse_specific": true }, "abuse_reporting_note": "Please note that the recommended way to file abuse complaints are located in the following links. To report abuse and illegal activity: https://www.google.com/contact/ For legal requests: http://support.google.com/legal Regards, The Google Team" }, "cost_sats": 6, "balance_remaining": 1494, "response_ms": 132, "endpoint": "/api/ip-intel" }

Good Uses

For the individual components, see IP Lookup and IP Abuse Check. Those pages are useful when you only need one side of the data.

Related APIs