Install Jentic One Beta

Connect the ipgeolocationapi.io API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ipgeolocationapi.io 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fipgeolocationapi.io%2Fipgeolocationapi" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fipgeolocationapi.io%2Fipgeolocationapi" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with ipgeolocationapi.io API.

Geolocate an IPv4 or IPv6 address, or the caller's own IP, with country, region, city, and connection details

Trim a lookup response to chosen fields with dot notation such as connection.asn, or drop fields with excludes

Convert a time between two IANA timezones with the from, to, and time parameters

Get sunrise, sunset, and moon events for an IP address or for lat and lon coordinates on a date

GET STARTED

Start building with ipgeolocationapi.io API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ipgeolocationapi.io API for, with concrete tasks.

★ Agent-driven IP triage

An AI agent reviewing suspicious sign-ins needs to know where each IP sits and who to contact about it. Through Jentic the agent searches for 'geolocate an IP address', loads the ipgeolocationapi.io lookup operation, and reads country, city, and connection details, then calls the abuse lookup for the RDAP contact. The key is attached at call time, so the agent works from the lookups without handling the credential.

Call GET /{ip} for 8.8.8.8 with fields set to ip,country,city,connection.asn, then call GET /abuse with ip 8.8.8.8 and report the abuse contact

Localising content by visitor IP

A web service picks the language, currency, and timezone to show based on the visitor's address. The caller IP lookup returns location, timezone, and currency for the request's own address, and lang localises the country name, so the service can render a regional default before the visitor chooses one.

Call GET / to look up the caller IP and return its country, timezone, and currency fields

Scheduling across timezones

An assistant booking a call between two cities converts the proposed time from one IANA timezone to another and checks local daylight for an in-person meeting. The timezone conversion read takes from, to, and an optional time, and the astronomy read returns sun and moon events for coordinates and a date.

Call GET /timezone/convert with from Europe/Dublin, to America/New_York, and time 2026-11-12T15:00, then call GET /astronomy with lat 40.71 and lon -74.01 for 2026-11-12

Log enrichment for analytics

A log pipeline adds network and client context to raw request records. The bulk lookup takes up to 100 comma-separated IPs on Business or Max keys, the ASN read returns the organisation and prefixes behind an autonomous system, and the user-agent parser splits the browser and device from each request.

Call GET /bulk with ips set to 1.1.1.1,8.8.8.8,9.9.9.9 and GET /useragent with a Chrome user-agent string, then merge both results into one record per request

Key Endpoints

9 endpoints — the ipgeolocationapi.

METHOD

PATH

DESCRIPTION

GET

/{ip}

Geolocate an IP address

GET

Look up the caller IP

GET

/bulk

Look up up to 100 IPs

GET

/abuse

Get the RDAP abuse contact for an IP

GET

/asn

Look up an ASN

GET

/timezone/convert

Convert between IANA timezones

GET

/useragent

Parse a user-agent string

GET

/{ip}

Geolocate an IP address

GET

Look up the caller IP

GET

/bulk

Look up up to 100 IPs

GET

/abuse

Get the RDAP abuse contact for an IP

GET

/asn

Look up an ASN

GET

/timezone/convert

Convert between IANA timezones

GET

/useragent

Parse a user-agent string

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring ipgeolocationapi.io by hand means deciding between the X-API-Key header and the key query parameter, and knowing which reads need a paid key. Through Jentic you install once, import ipgeolocationapi.io from the API Directory, store the key once, and your agent calls it.

Permission scoping

Each ipgeolocationapi.io capability is its own operation, so a rule can bound your agent to the lookups it needs, such as the IP and abuse reads. You choose the operations it may call, so the paid bulk lookup is not included unless you add it.

Credential isolation

Your ipgeolocationapi.io key 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.

Intent-based discovery

Agents search Jentic by intent such as 'geolocate an IP address' or 'convert a time between timezones', and Jentic returns the matching ipgeolocationapi.io operation with its input schema so the agent calls the right endpoint.

FAQs

Specific to using ipgeolocationapi.io API through Jentic.

What authentication does the ipgeolocationapi.io API use?

Per its OpenAPI spec, the API declares an API key sent in the X-API-Key header, applied to every operation. The IP lookup and bulk operations also accept the key as a key query parameter. Through Jentic the key is stored by your own instance and attached at call time, so the agent never sees it.

What are the rate limits for the ipgeolocationapi.io API?

The spec states a free allowance of 5,000 requests a day with no credit card, and marks bulk lookups and the security and company blocks as paid. It does not list per-plan limits; check https://ipgeolocationapi.io for current plans.

Can I look up many IP addresses at once with the ipgeolocationapi.io API?

Yes, on paid plans. GET /bulk takes up to 100 comma-separated IPs in the ips parameter and needs a Business or Max key. For single addresses, GET /{ip} accepts fields and excludes to keep responses small.

Is there an ipgeolocationapi.io MCP server?

You don't need an MCP server to give your agent ipgeolocationapi.io. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the lookup, timezone, and ASN operations on demand without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the ipgeolocationapi.io API?

Yes. Write a rule that allows only GET /{ip} and GET /abuse, for example, and the agent can geolocate addresses and fetch abuse contacts but cannot run paid bulk lookups against your quota. Every call it makes is logged.

How do I geolocate an IP address through Jentic?

Search Jentic for 'geolocate an IP address', load the GET /{ip} operation, and execute it with the address and an optional fields list such as ip,country,connection.asn. To run it on your own infrastructure, install Jentic One from its GitHub repo.

ipgeolocationapi.io API

AI ReadinessFoundational (D-)42/100

See full scorecard

Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey9 EndpointsREST

For Agents

Look up where an IP address is, which network owns it, and who handles its abuse reports, plus timezone conversion, astronomy times, and user-agent parsing in one key.

Use for: Find the country and city for an IP address, Get the abuse contact for an IP that is sending spam, Convert 09:00 in Europe/Dublin to America/New_York, Retrieve sunrise and sunset times for a pair of coordinates

Not supported: Does not geocode street addresses, calculate routes, or render maps. Use for IP address geolocation and related network lookups only.

The ipgeolocationapi.io API resolves an IPv4 or IPv6 address to its location, connection, timezone, and currency details, with optional security and company blocks on paid plans. Beyond the IP lookup it converts times between IANA timezones, returns sun and moon events for an IP or coordinates, parses user-agent strings, and looks up ASN details and abuse contacts through RDAP. Responses are drop-in compatible with ipwho.is and can be trimmed with fields and excludes, localised with lang, or returned as JSON, XML, or CSV.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

10%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

31%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

27%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

47%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ipgeolocationapi.io API to your agent

Capabilities

Start building with ipgeolocationapi.io API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

ipgeolocationapi.io API

Jentic AI Readiness Score

ipgeolocationapi.io API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness