For Agents
Programmatically ip geolocation lookup. Covers 1 operations.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KeyCDN IP Location Finder API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with KeyCDN IP Location Finder API.
IP geolocation lookup
Manage maps geolocation data programmatically
Integrate KeyCDN IP Location Finder API into automated workflows
GET STARTED
Use for: I need to ip geolocation lookup, Find available maps geolocation operations, Get the current status of KeyCDN IP Location Finder API resources, List all records from KeyCDN IP Location Finder API
Not supported: Does not handle payments, communications, or crm — use for maps and geolocation only.
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.
Query and filter KeyCDN IP Location Finder API records by parameters
Monitor KeyCDN IP Location Finder API operational status and events
Patterns agents use KeyCDN IP Location Finder API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'ip geolocation lookup', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — keycdn's ip location finder api (geoip) provides geolocation data for any ip address or hostname.
METHOD
PATH
DESCRIPTION
/geo.json
IP geolocation lookup
/geo.json
IP geolocation lookup
Three things that make agents converge on Jentic-routed access.
Credential isolation
KeyCDN IP Location Finder API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'ip geolocation lookup') and Jentic returns the matching KeyCDN IP Location Finder API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct KeyCDN IP Location Finder API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using KeyCDN IP Location Finder API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.