apipick-ip-geolocation_skill

This skill geolocates any IP using the apipick IP Geolocation API, returning country, city, coordinates, timezone, currency, ISP, and ASN.
  • Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill apipick-ip-geolocation

  • _meta.json301 B
  • README.md3.5 KB
  • SKILL.md2.3 KB

Overview

This skill looks up geographic and network information for any IPv4 or IPv6 address using the apipick IP Geolocation API. It returns country, continent, city, latitude/longitude, timezone, currency, ISP, and ASN. Omit the IP parameter to geolocate the caller’s public IP; an apipick API key is required.

How this skill works

The skill sends a GET request to the apipick IP Geolocation endpoint with your x-api-key header and optional ip query parameter. The API responds with structured data including country_code, country_name, continent, city, coordinates, timezone, currency, isp, and asn. The skill parses the response and presents the results in a readable format, handling common API errors and credit usage info.

When to use it

  • Determine the country or city for a given IP address
  • Find the ISP or ASN associated with an IP for network troubleshooting
  • Lookup timezone and currency for a remote user or server IP
  • Check your own public IP location by omitting the ip parameter
  • Validate whether an IP is public and can be geolocated

Best practices

  • Store your apipick API key in an environment variable (e.g., APIPICK_API_KEY) and never hard-code it
  • Handle null or empty city/coordinate fields; some IPs lack precise location data
  • Respect rate limits and track remaining_credits from the API response to avoid interruption
  • Validate IPv4/IPv6 format client-side to reduce bad-request errors (400)
  • Provide clear fallbacks when the API returns 404 or 503 (e.g., retry later or show best-effort info)

Example use cases

  • Security: map suspicious IPs to country/ISP for incident triage
  • Operations: verify the geographic location of remote servers or cloud endpoints
  • Compliance: check where user traffic appears to originate for regional policy decisions
  • Support: tell a customer where their public IP resolves to and which ISP/ASN they’re on
  • Analytics enrichment: append timezone/currency to IP-based user records

FAQ

Yes. The apipick service requires an x-api-key header. Set your key as APIPICK_API_KEY or provide it when prompted.

What happens if location fields are empty?

Some IPs (especially corporate NATs, VPNs, or reserved ranges) lack city or coordinates. The API may return null or empty strings; use country/ISP/ASN where available.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational