canonical: https://jentic.com/apis/ipasis.com/ipasis

# Ipasis GeoAPI

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.

## For AI 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.

## Scope

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

## Capabilities

- 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

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **IP lookup** — Geolocation, ASN, company, privacy flags, abuse contacts, and domains for an IP
- **Email validation** — Email risk scoring by query or JSON body, optionally combined with an IP

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 68 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 18 / 100
  - Agent Usability: 94 / 100
  - Security: 42 / 100
  - AI Discoverability: 53 / 100
- **View full report:** https://jentic.com/apis/ipasis.com/ipasis/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **IP99 IP risk and geolocation API** — Evidence-based IP risk verdicts with freshness and point-in-time history
- **ipdata** — IP geolocation with threat and proxy flags
- **AbuseIPDB** — Community-reported IP abuse database
- **Kickbox** — Mailbox-level email verification

## FAQ

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