Install Jentic One Beta

Connect the Ipasis GeoAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ipasis GeoAPI, 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%2Fipasis.com%2Fipasis" | 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%2Fipasis.com%2Fipasis" | 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 Ipasis GeoAPI API.

Look up the city, region, country, postal code, and timezone for an IP address

Flag VPN, proxy, Tor, and hosting IPs through the privacy block of a lookup

Read the ASN, company, and abuse contact behind an IP

Include raw provider and feed details in a lookup with the details flag

Score an email address for risk, optionally combined with the request IP

GET STARTED

Start building with Ipasis GeoAPI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Ipasis GeoAPI API for, with concrete tasks.

★ AI fraud agent scoring signups by email and IP

A developer's agent connected through Jentic finds the Ipasis operations by intent and calls them with the key injected at execution time. For each new signup it validates the email with the signup IP attached for combined risk scoring and checks the IP's privacy flags, then holds accounts that look risky for review, without the key entering the agent's context.

POST /v1/validate-email with email 'new.user@example.org' and ip '198.51.100.23', then GET /v1/lookup with ip '198.51.100.23' and report the risk and privacy flags

Blocking anonymised traffic at checkout

Payment fraud often arrives through anonymising networks. The IP lookup returns a privacy block flagging VPN, proxy, Tor, and hosting addresses along with location and ASN, so a checkout service can add friction for orders placed from hosting providers or Tor.

Call GET /v1/lookup with the order's IP and flag the order if the privacy block marks it as Tor, VPN, proxy, or hosting

Reporting abusive IPs

When an IP is attacking a service, the operator needs to know who to contact. The lookup returns the abuse contact, company, ASN, and domains for the address, so an incident tool can draft an abuse report to the right network owner.

Call GET /v1/lookup with ip '192.0.2.44' and details 'true', then draft an abuse report addressed to the returned abuse contact

Key Endpoints

4 endpoints — the ipasis geoapi returns real-time ip intelligence for fraud prevention: geolocation, asn, privacy flags for vpn, proxy, tor, and hosting use, abuse contacts, and company information for a given ip address.

METHOD

PATH

DESCRIPTION

GET

/v1/lookup

IP geolocation, privacy flags, and ownership

GET

/v1/validate-email

Validate an email by query

POST

/v1/validate-email

Validate an email by JSON body

GET

/v1/lookup

IP geolocation, privacy flags, and ownership

GET

/v1/validate-email

Validate an email by query

POST

/v1/validate-email

Validate an email by JSON body

Why Jentic?

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

Setup

Wiring Ipasis by hand means picking one of three credential forms, bearer, X-API-Key header, or key query parameter, and keeping the key out of URLs and logs when the query form is the easy option. Through Jentic you install once, import Ipasis from the API Directory, store the key once, and your agent calls it.

Permission scoping

Ipasis takes the IP or email as a query or body parameter rather than a path segment, so rules bound which operations your agent may call, not which address it checks. You choose the operations it may call, so email validation is not included unless you add it.

Credential isolation

Your Ipasis API 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 'check IP reputation' or 'validate an email address', and Jentic returns the matching Ipasis operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Ipasis GeoAPI API through Jentic.

What authentication does the Ipasis GeoAPI use?

Per its OpenAPI spec, Ipasis accepts any one of three forms of the same credential: a bearer token in the Authorization header, an API key in the `X-API-Key` header, or the key in a `key` query parameter. The /healthz endpoint needs no credential. Through Jentic the key is stored by your own instance and attached as a header at call time.

Can I detect VPN and Tor traffic with the Ipasis GeoAPI?

Yes. GET /v1/lookup takes an ip and returns a privacy block with VPN, proxy, Tor, and hosting flags, plus city, region, country, ASN, company, and abuse contact details. Set details to true to include the raw provider and feed data.

What are the rate limits for the Ipasis GeoAPI?

The OpenAPI spec does not specify numeric rate limits, though GET /v1/lookup documents a 429 response when the limit is exceeded. Check https://ipasis.com for current plan limits.

Is there an Ipasis MCP server?

You don't need an MCP server to give your agent Ipasis. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the IP lookup and email validation operations it needs, discovered on demand rather than loaded into its context.

Can I limit what my agent is allowed to do with Ipasis?

Yes. For example, write a rule that allows only GET /v1/lookup, so the agent can check IP addresses but cannot submit email addresses for validation, and every call it makes is logged.

How do I check an IP's reputation through Jentic?

Import the Ipasis GeoAPI from the Jentic API Directory and store your API key once. Your agent searches for 'check IP reputation', gets GET /v1/lookup with its schema, and passes the required ip parameter. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Ipasis GeoAPI

AI ReadinessNon-Ready (F)39/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityThreat Detectionbearer, apiKey4 EndpointsREST

For Agents

Look up an IP's location, ASN, company, abuse contacts, and VPN, proxy, Tor, or hosting flags, and score an email address for risk alongside its IP.

Use for: Check whether this checkout IP is a Tor exit or VPN, Get the company and ASN that own an IP address, Find the abuse contact for an IP that is attacking us, Validate this signup email together with the signup IP

Not supported: Does not handle blocking traffic, firewall configuration, or sending email. Use for IP intelligence lookups and email risk validation only.

The Ipasis GeoAPI returns real-time IP intelligence for fraud prevention: geolocation, ASN, privacy flags for VPN, proxy, Tor, and hosting use, abuse contacts, and company information for a given IP address. Its lookup is built as a hot-path call that can run inline on a signup or checkout request, with an optional details flag that adds the raw provider and feed data. A companion email validation operation scores an email address for risk and can combine that score with the IP the request came from.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

75%

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: BSignals: 4

13%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

44%

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

15%

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.

57%

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: D-Signals: 1

42%

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: CSignals: 1

53%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Ipasis GeoAPI to your agent

Capabilities

Start building with Ipasis GeoAPI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Ipasis GeoAPI

Jentic AI Readiness Score

Ipasis GeoAPI

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