Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Who Hosts This 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%2Fwho-hosts-this.com%2Fwho-hosts-this" | shStep 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%2Fwho-hosts-this.com%2Fwho-hosts-this" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Who Hosts This API.
Discover the hosting provider for a web site
View usage details for the current billing period
Integrate Who Hosts This API into automated workflows
Query and filter Who Hosts This API records by parameters
Monitor Who Hosts This API operational status and events
GET STARTED
Patterns agents use Who Hosts This API for, with concrete tasks.
★ Cloud Infrastructure Operations
Use the Who Hosts This API to perform cloud infrastructure operations programmatically. The API provides 2 endpoints covering core functionality including discover the hosting provider for a web site, view usage details for the current billing period.
Call GET /Detect to discover the hosting provider for a web site
Data Retrieval and Monitoring
Query Who Hosts This API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Who Hosts This API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Who Hosts This API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'discover the hosting provider for a web site', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — discover the hosting provider for any web site.
METHOD
PATH
DESCRIPTION
/Detect
Discover the hosting provider for a web site
/Status
View usage details for the current billing period
/Detect
Discover the hosting provider for a web site
/Status
View usage details for the current billing period
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Who Hosts This API by hand means registering for an API key, appending it as a query parameter on each request, and handling its detect and status responses yourself. Through Jentic you install once, import the Who Hosts This API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Who Hosts This API travels its target in the request, not as a path resource, so limit the agent to the operations it needs, such as Detect and Status. You choose the operations it may call, so nothing beyond that set runs unless you add it.
Credential isolation
Your Who Hosts This 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 'find the hosting provider for a domain', and Jentic returns the matching Who Hosts This operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Who Hosts This API through Jentic.
What authentication does the Who Hosts This API use?
The Who Hosts This API uses an API key passed in the `key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I discover the hosting provider for a web site with the Who Hosts This API?
Yes. Use the GET /Detect endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Who Hosts This API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I discover the hosting provider for a web site through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'discover the hosting provider for a web site'. Jentic returns the matching Who Hosts This API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Who Hosts This API have?
The Who Hosts This API exposes 2 endpoints covering detect, status operations.
Can I limit what my agent is allowed to do with the Who Hosts This API?
Yes. Because you run Jentic One yourself, you decide which of the Who Hosts This API operations your agent may call, so you can grant only GET /Detect for hosting-provider lookups, only GET /Status for billing-period usage checks, or both. The target site travels in the request rather than as a path resource, so nothing outside the operations you allow can run unless you add it. Your API key is stored encrypted by your own instance and injected at execution time, keeping it out of the agent's context.
For Agents
Programmatically discover the hosting provider for a web site, view usage details for the current billing period. Covers 2 operations with apiKey authentication.
Use for: I need to discover the hosting provider for a web site, I want to view usage details for the current billing period, Get the current status of Who Hosts This API resources, List all records from Who Hosts This API
Not supported: Does not handle payments, communications, or crm - use for cloud infrastructure only.
Discover the hosting provider for any web site. The API exposes 2 endpoints secured with apiKey authentication.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>