canonical: https://jentic.com/apis/who-hosts-this.com/who-hosts-this # Who Hosts This API Discover the hosting provider for any web site. The API exposes 2 endpoints secured with apiKey authentication. ## For AI agents Programmatically discover the hosting provider for a web site, view usage details for the current billing period. Covers 2 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for cloud infrastructure only. ## Capabilities - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'discover the hosting provider for a web site', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/Detect` | Discover the hosting provider for a web site | | GET | `/Status` | View usage details for the current billing period | ## Key resources - **Detect** — Operations for Detect - **Status** — Operations for Status ## 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:** 37 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 23 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 69 / 100 - **View full report:** https://jentic.com/apis/who-hosts-this.com/who-hosts-this/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 ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Amazonaws** — Alternative cloud infrastructure API - **Azure** — Alternative cloud infrastructure API - **Googleapis** — Complementary cloud infrastructure API - **Digitalocean** — Complementary cloud infrastructure API ## FAQ ### 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.