IP Lookup Skill

"Whose IP is this?" comes up in log triage, abuse reports, debugging, and plain curiosity — and keyless services answer it: ipify for "what's my IP," ip-api.com for "what's that IP." This skill fetches, reads the fields that matter (ASN and ISP are usually the real answer; city is a guess wearing coordinates), and holds the two honesty lines the domain needs: IP geolocation is approximate, and none of this is a person's identity.

What This Skill Produces

• The lookup — country/region/city, ISP, org, ASN, and the proxy/hosting flags where available
• The interpretation — what the fields actually establish ("a Hetzner datacenter IP in Falkenstein" vs. "a residential Comcast line, roughly Denver")
• Your-own-IP answers — v4 and v6 when both matter
• The command — exact curl, rerunnable

Required Inputs

Ask for these if not provided:

• The IP (or "mine") — v4 or v6; a hostname is fine (it gets resolved first — say so)
• The purpose — log triage wants the ASN/hosting read; debugging wants "is my egress IP what I think"; abuse-report prep wants the network owner — the interpretation follows it

Framework: The Calls and the Honesty Lines

1. Your own IP: curl -s https://api.ipify.org (v4) · curl -s https://api64.ipify.org (v6-preferring) — one word of output, script-safe. Also embedded in most routers' complaints, but this is the clean answer.
2. The lookup: curl -s "http://ip-api.com/json/8.8.8.8?fields=status,country,regionName,city,isp,org,as,proxy,hosting,query" — the fields parameter keeps it tight; proxy and hosting flags answer the VPN/datacenter question directly. Free tier is HTTP and rate-limited (~45/min) — fine for lookups, not for bulk scans.
3. ASN is the real identity: "AS15169 Google LLC" tells you more than any city field — datacenter ranges geolocate to corporate registrations, not servers. Lead the interpretation with network ownership; treat city as "roughly."