canonical: https://jentic.com/apis/tools.keycdn.com/keycdn-ip-location-finder-api

# Tools Keycdn KeyCDN IP Location Finder API

KeyCDN's IP Location Finder API (geoip) provides geolocation data for any IP address or hostname. It returns details including country, region, city, postal code, ISP, ASN, coordinates, timezone and more. A custom User-Agent header containing 'keycdn-tools:https://yourdomain.com' is required for authentication. The API exposes 1 endpoints.

## For AI agents

Programmatically ip geolocation lookup. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- IP geolocation lookup
- Manage maps geolocation data programmatically
- Integrate KeyCDN IP Location Finder API into automated workflows
- Query and filter KeyCDN IP Location Finder API records by parameters
- Monitor KeyCDN IP Location Finder API operational status and events

## Use cases

### Maps and Geolocation Operations

Use the KeyCDN IP Location Finder API to perform maps geolocation operations programmatically. The API provides 1 endpoints covering core functionality including ip geolocation lookup.

Example prompt: Call GET /geo.json to ip geolocation lookup

### Data Retrieval and Monitoring

Query KeyCDN IP Location Finder API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary KeyCDN IP Location Finder API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call KeyCDN IP Location Finder API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'ip geolocation lookup', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/geo.json` | IP geolocation lookup |

## Key resources

- **Geolocation** — IP geolocation lookup

## Why Jentic

- **Setup:** Wiring the KeyCDN IP Location Finder by hand means pointing at the tools.keycdn.com host, formatting the geo.json lookup request, and coding your own response parsing. Through Jentic you install once, import the KeyCDN IP Location Finder API from the API Directory, store any needed credential once, and your agent calls it.
- **Permission scoping:** This API exposes a single read-only IP geolocation lookup, so scope the agent to just that operation. You choose which operations are allowed, and only the lookup you include is callable.
- **Credential handling:** Any KeyCDN credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up the geolocation of an IP address', and Jentic returns the matching KeyCDN operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the KeyCDN IP Location Finder API use?

The KeyCDN IP Location Finder API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I ip geolocation lookup with the KeyCDN IP Location Finder API?

Yes. Use the GET /geo.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the KeyCDN IP Location Finder API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I ip geolocation lookup through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'ip geolocation lookup'. Jentic returns the matching KeyCDN IP Location Finder API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the KeyCDN IP Location Finder API have?

The KeyCDN IP Location Finder API exposes 1 endpoints covering geolocation operations.

### Can I limit what my agent is allowed to do with the KeyCDN IP Location Finder API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use. This API exposes a single read-only IP geolocation lookup (GET /geo.json), so you can scope the agent to just that one call and nothing else is reachable. Since it is a read-only lookup, the agent can retrieve location data for an IP or hostname without any ability to write or change anything.