Install Jentic One Beta

Connect the IPWhois.net API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IPWhois.net 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%2Fipwhois.net%2Fipwhois" | 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%2Fipwhois.net%2Fipwhois" | 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 IPWhois.net API.

Geolocate an IPv4 or IPv6 address with country, city, postal_code, latitude, longitude, and accuracy_radius_km

Read the ISP, ASN, and timezone of an address, or of the caller's own IP, trimmed to chosen paths with fields

Check whether an IP is listed on a DNS blacklist, singly or in a paid batch

Resolve a MAC address or OUI to its vendor company, block type, and randomized or multicast flags

GET STARTED

Start building with IPWhois.net API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use IPWhois.net API for, with concrete tasks.

★ Agent-led IP and device investigation

An AI agent triaging a network alert needs to know where an address sits, whether it is blacklisted, and what hardware is on the local segment. Through Jentic the agent searches for 'look up an IP address', loads the IPWhois.net lookup, and then calls the blacklist and MAC reads with the same key attached at call time. It reports location, ISP, listing status, and device vendor in one answer.

Call GET /ip/{ip} for 203.0.113.7 with fields location,network.isp, then GET /blacklist/{ip} for the same address and GET /mac/{mac} for 00:1A:2B:3C:4D:5E, and summarise the results

Mail server reputation checks

An email operations team checks whether its sending IPs appear on DNS blacklists before a campaign. The blacklist read returns a listed flag for one address, and on paid plans the batch read checks many IPs in one call with per-list detail.

Call POST /blacklist/batch with ips 198.51.100.10 and 198.51.100.11 and list any address where listed is true

Network asset inventory

An IT administrator labelling devices from a switch's MAC table needs the manufacturer of each address. The MAC read returns the vendor company, country, and block type such as MA-L, and flags randomized and locally administered addresses so phones with private MACs are not mislabelled.

Call GET /mac/{mac} for each address in a list and record vendor.company, block.type, and is_randomized

Quota-aware batch geolocation

A data job geolocating a day's access logs needs to stay inside its plan. The batch lookup takes an ips array on paid plans, and the usage read returns the key's plan, rate limit, and quota without counting against it, so the job can pace itself.

Call GET /usage to read the remaining quota, then call POST /ip/batch with ips 8.8.8.8 and 1.1.1.1 and store each result's country_code and asn

Key Endpoints

8 endpoints — the ipwhois.

METHOD

PATH

DESCRIPTION

GET

/ip/{ip}

Geolocate an IP address

GET

/ip

Look up the caller's own IP

POST

/ip/batch

Batch IP lookup (paid plans)

GET

/blacklist/{ip}

Check DNS blacklist status

GET

/mac/{mac}

Look up a MAC vendor

GET

/mac/search

Search OUI blocks by vendor (paid plans)

GET

/usage

Read plan and quota

GET

/ip/{ip}

Geolocate an IP address

GET

/ip

Look up the caller's own IP

POST

/ip/batch

Batch IP lookup (paid plans)

GET

/blacklist/{ip}

Check DNS blacklist status

GET

/mac/{mac}

Look up a MAC vendor

GET

/mac/search

Search OUI blocks by vendor (paid plans)

GET

/usage

Read plan and quota

Why Jentic?

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

Setup

Wiring IPWhois.net by hand means picking one of three ways to send the key, tracking which reads need a paid plan, and pacing calls to the per-second limit. Through Jentic you install once, import IPWhois.net from the API Directory, store the key once, and your agent calls it.

Permission scoping

IPWhois.net splits IP, blacklist, MAC, and usage reads into separate operations, so a rule can bound your agent to the ones it needs, such as single IP lookups. You choose the operations it may call, so paid batch reads like POST /ip/batch are not included unless you add them.

Credential isolation

Your IPWhois.net 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 'look up an IP address' or 'check an IP blacklist', and Jentic returns the matching IPWhois.net operation with its input schema so the agent calls the right endpoint.

FAQs

Specific to using IPWhois.net API through Jentic.

What authentication does the IPWhois.net API use?

Per its OpenAPI spec, every call needs an API key, accepted in the X-API-Key header, as an Authorization: Bearer token, or in the key query parameter. One key works for the IP, blacklist, and MAC services. 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 IPWhois.net API?

The spec states a free key allows 1,000 IP, 1,000 blacklist, and 1,000 MAC lookups a day at 1 request per second with basic fields. Paid plans are metered per month: Starter 250,000 requests at 5 per second, Pro 1,500,000 at 15 per second, and Business 6,000,000 at 30 per second. See https://ipwhois.net/pricing for current prices.

Can the IPWhois.net API identify a device from its MAC address?

Yes. GET /mac/{mac} returns the vendor company and country, the block type such as MA-L or MA-S, and flags for multicast, locally administered, and randomized addresses. On paid plans GET /mac/search lists the OUI blocks registered to a vendor name.

Is there an IPWhois.net MCP server?

You don't need an MCP server to give your agent IPWhois.net. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the IP, blacklist, and MAC operations it needs without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the IPWhois.net API?

Yes. Write a rule that allows only GET /ip/{ip} and GET /usage, for example, and the agent can geolocate single addresses and check its quota but cannot run the batch reads that spend paid allowance faster. Every call it makes is logged.

How do I look up an IP address through Jentic?

Search Jentic for 'look up an IP address', load the GET /ip/{ip} operation, and execute it with the address and an optional fields value such as location,network.isp. To run it on your own infrastructure, install Jentic One from its GitHub repo.

IPWhois.net API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey, bearer8 EndpointsREST

For Agents

Geolocate IP addresses, check them against DNS blacklists, and identify the vendor behind a MAC address, with the key's remaining quota returned on every call.

Use for: Find the city and ISP for an IP address, Check whether this IP is on a DNS blacklist, Get the vendor of a MAC address from a network scan, List all OUI blocks registered to Cisco

Not supported: Does not return domain WHOIS records, geocode street addresses, or detect VPNs. Use for IP geolocation, DNS blacklist, and MAC vendor lookups only.

The IPWhois.net API returns the location, timezone, ISP, ASN, and connection type of an IPv4 or IPv6 address, including latitude, longitude, accuracy radius, and an is_eu flag. The same key also checks whether an address is listed on a DNS blacklist and resolves a MAC address or OUI to its registered vendor and address block. Paid plans add the full field set, batch lookups for IPs and blacklists, and a search for every OUI block registered to a vendor name, and every response carries a meta block with the key's plan and remaining quota.

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

24%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

53%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the IPWhois.net API to your agent

Capabilities

Start building with IPWhois.net API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

IPWhois.net API

Jentic AI Readiness Score

IPWhois.net 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