Install Jentic One Beta

Connect the IP2WHOIS API to your agent

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

Look up the registrar and registrant of any registered domain across 1,221 gTLDs and 634 ccTLDs

Return the creation, updated, and expiry dates for a domain in a single call

Pull the administrative, technical, and billing contacts where the registrar exposes them

List the name servers and DNSSEC status configured for a domain

Surface registrar status flags to spot lock, redemption, and pending-delete states

GET STARTED

Start building with IP2WHOIS API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use IP2WHOIS API for, with concrete tasks.

★ Domain Portfolio Expiry Watch

Brand and IT teams managing large domain portfolios can call IP2WHOIS for each domain weekly, read expiry_date and registrar_status, and surface domains that are within the renewal window or have slipped into redemption. The 1,221 gTLD and 634 ccTLD coverage matters when the portfolio includes country-code domains that some WHOIS providers do not parse cleanly.

For each domain in a portfolio file, call IP2WHOIS and return the ones whose expiry_date is within the next 30 days.

Brand Protection and Typosquat Hunting

Trust and brand teams can pull WHOIS for newly registered look-alike domains, read the registrar and registrant fields, and decide whether to file a takedown or send a UDRP notice. The contact and name-server fields help cluster typosquats run by the same operator.

Look up WHOIS for a flagged look-alike domain and return the registrar, registrant organisation, and name servers for the takedown report.

Compliance and Vendor Onboarding

Compliance teams onboarding a new vendor can verify that the domain on a contract is actually held by the vendor's organisation rather than a personal registrant or a privacy-proxy service. IP2WHOIS surfaces the registrant_organization and registrar fields where the registrar exposes them.

Look up WHOIS for a vendor domain and report whether registrant_organization matches the legal entity on the contract.

Agent-Driven Domain Audit

An AI agent connected via Jentic can audit a list of domains, classify them by registrar and expiry window, and produce a structured report. The agent searches Jentic by intent rather than building a WHOIS parser by hand, which matters when the portfolio mixes gTLDs and ccTLDs.

Audit a CSV of 100 domains and return a JSON summary grouped by registrar, with expiry_date and registrar_status per row.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for ip2whois api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v2

Domain WHOIS lookup

GET

/v2

Domain WHOIS lookup

Why Jentic?

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

Setup

Wiring IP2WHOIS by hand means registering for a key, passing it as the 'key' query parameter to the /v2 endpoint on api.ip2whois.com, and normalizing the registrar and expiry fields yourself. Through Jentic you install once, import IP2WHOIS from the API Directory, store the key once, and your agent calls it.

Permission scoping

IP2WHOIS exposes a single read-only WHOIS lookup where the domain travels as a query parameter, so scope the agent to the operations it needs, such as looking up a domain's WHOIS record. It remains a lookup client and cannot act beyond the operations you allow.

Credential isolation

Your IP2WHOIS API key is stored once, encrypted, by your own Jentic One instance and injected as the 'key' query parameter 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 WHOIS' or 'find domain expiry', and Jentic returns the IP2WHOIS operation with its input schema, including the optional format parameter, so the agent calls the right endpoint without reading the docs.

FAQs

Specific to using IP2WHOIS API through Jentic.

Why is there no official OpenAPI spec for IP2WHOIS API?

IP2WHOIS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call IP2WHOIS API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the IP2WHOIS API use?

The endpoint accepts an API key as the 'key' query parameter. Through Jentic the key is held in the encrypted vault and appended at execution time so the raw key never enters the agent context.

Can the IP2WHOIS API look up country-code TLDs?

Yes. Coverage spans 1,221 generic TLDs and 634 country-code TLDs, which is broader than many WHOIS providers and matters for portfolios that include uncommon ccTLDs.

What are the rate limits for the IP2WHOIS API?

Throughput is governed by the credit balance on the API key rather than a per-minute cap; each lookup consumes one credit. Remaining credits are visible in the IP2WHOIS account dashboard.

How do I look up a domain through Jentic?

Search Jentic for 'look up WHOIS for a domain', load the schema for GET /v2, and execute with the domain. Run pip install jentic, then await client.search, await client.load, await client.execute.

Does IP2WHOIS return the registrar status flags?

Yes. The response includes the registrar_status array (e.g. clientTransferProhibited, redemptionPeriod, pendingDelete) so an agent can spot domains that are locked, expiring, or in dispute.

Can I limit what my agent is allowed to do with the IP2WHOIS API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use, and IP2WHOIS exposes only a single read-only WHOIS lookup on the /v2 endpoint. You can scope the agent to just that domain lookup, so it can read the registrar, registrant, name servers, expiry date, and registrar status flags but cannot act beyond the operations you allow. It stays a lookup client, with the API key held by your own instance and injected only at execution time.

IP2WHOIS API

Name: IP2WHOIS API
Brand: IP2WHOIS API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticData EnrichmentCompany DataapiKey1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Look up the registrar, registrant, expiry date, and name servers for any domain so an agent can run ownership, compliance, or brand-protection checks.

Use for: I need to look up WHOIS data for a domain, Get the registrar and registrant for example.com, Find the expiry date for a list of domains, Retrieve the name servers configured for a domain

Not supported: Does not handle DNS resolution, IP geolocation, or registrar account management - use for domain WHOIS lookups only.

Jentic publishes the only available OpenAPI specification for IP2WHOIS API, keeping it validated and agent-ready. IP2WHOIS is a hosted domain WHOIS lookup service that returns registrar, registrant, administrative and technical contacts, name servers, creation and expiry dates, and registrar status flags for any registered domain. The single-endpoint surface supports 1,221 generic TLDs and 634 country-code TLDs, which makes it broadly useful for compliance, brand protection, and ownership audits across uncommon domains.

Jentic One on Github View OpenAPI Document