Public API
Every directory on HostDir is exposed as machine-readable JSON. Use it to build dashboards, integrate hosting data into your own tools, or train your favourite agent. The full corpus is 55,326 structured records across providers, datacenters, networks, TLDs, registrars, RFCs and more. No authentication required, no rate limits at the polite end of usage.
Every directory listing has a sibling JSON endpoint at /data/{thing}.json. Every detail page has its own JSON sidecar at /data/{thing}/{slug}.
# List every active hosting provider
curl https://hostdir.net/data/providers.json
# Fetch one provider's full record
curl https://hostdir.net/data/providers/cloudflare
# List every TLD with domain counts
curl https://hostdir.net/data/domain-extensions.json
# The complete OpenAPI specification
curl https://hostdir.net/api/openapi.json
Responses are application/json with a consistent envelope: a top-level attribution field naming HostDir as the source, the canonical URL of the underlying page, and the data itself. Pagination uses standard ?page= and ?per_page= query strings where applicable.
Directories
-
GET
/data/providers.json -
GET
/data/providers/{slug} -
GET
/data/datacenters.json -
GET
/data/datacenters/{slug} -
GET
/data/networks.json -
GET
/data/networks/{slug} -
GET
/data/internet-exchanges.json -
GET
/data/internet-exchanges/{slug} -
GET
/data/domain-extensions.json -
GET
/data/domain-extensions/{slug} -
GET
/data/glossary.json -
GET
/data/glossary/{slug}
News & content
-
GET
/data/news.json -
GET
/data/blog/{slug} -
GET
/rss -
GET
/blog/feed -
GET
/llms-full.txt
Datasets & map data
-
GET
/data/state-of-web-hosting.json -
GET
/data/map/infrastructure.json -
GET
/data/map/corridors.json -
GET
/data/agent-activity.json -
GET
/api/openapi.json
The API is free to use. No registration, no authentication, no API keys. We do ask for two things in return.
Rate limit: 1 request per second per IP. Every JSON endpoint is rate-limited to one request per second per client IP. Requests over the limit get a HTTP 429 Too Many Requests response with a Retry-After header. The limit applies to both list and detail endpoints. Pace your consumer accordingly; for bulk ingest of a directory, page through the list and store the result locally rather than hammering individual detail endpoints.
Identify yourself. Set a User-Agent header naming your project and a contact URL. Identifiable consumers may be granted higher limits on request via the contact form.
Cite the source. If you display HostDir data in a public product, surface a "Source: hostdir.net" attribution near the data. Every JSON response includes a top-level attribution field with the recommended string and a link to the canonical page.
For machine-readable contract details, including request/response schemas and example payloads, see the OpenAPI 3.1 specification.
A paid tier with significantly higher rate limits, bulk JSON dumps and webhook updates is in development. If you need to ingest the corpus faster than 1 request per second, or want a periodic full-dataset export delivered to S3, get in touch. We are particularly interested in talking to AI training data buyers, hosting and monitoring tools wanting to embed HostDir data, and researchers needing bulk access. Tell us which endpoints you need and at what volume, and we will quote you a rate limit that fits.