inetGeek docs
HTTP feeds

Overview

Free, unauthenticated, read-only JSON and Markdown

Everything the MCP server returns is also published as plain HTTP. There is no key, no sign-up and no write endpoint.

curl -s https://inetgeek.com/providers/core.json | jq '.providers[] | select(.id=="plausible") | .facts.minimum_paid_price'

The OpenAPI document describes every path below and is checked against the live responses by a script in the repository, so a field that appears here appears in the feed.

Feeds

PathWhat it is
/providers/core.jsonEvery provider with its facts: value, source URL and date. About 1.6 MB
/providers.jsonThe same plus the verbatim excerpt behind every fact. About 3 MB
/providers/keys.jsonOnly which fact keys each provider documents
/scores.jsoniScore per provider per category, with intervals and pillars
/plan.jsonPlanner data: one pick per layer with pickBasis, plus every ranked candidate
/usage-pricing.jsonPlans priced by volume, with quote-only rows marked
/startup-credits.jsonStartup credit programmes as stated
/ledger.jsonPages read and found silent, and where a vendor's own pages disagree
/changelog.jsonEvery recorded change to a published fact
/search-index.jsonEvery published page, title and description
/{section}/{slug}.mdOne provider's fact sheet as Markdown
/compare/{pair}.mdA curated comparison as Markdown
/stacks/{framework}.mdHosts that document support for a framework
/api/dns, /api/spf, /api/propagationLive DNS, SPF and propagation checks

Each is documented, with its response schema and a request console, in the reference.

Reading the data honestly

  • A blank is not a "no". unstated on a provider means a vendor page was read on a date and did not state the criterion. A missing fact means nobody has looked. /ledger.json keeps these apart, and records a third thing: two pages of one vendor that contradict each other, with no value recorded.
  • A rank is usually an ordering. In /scores.json, read low and high with overall, and treat distinct: false as "ordering, not finding".
  • A tie is a tie. In /plan.json, pickBasis: "tie" means the pick was separated from coEqual by nothing but the alphabet.
  • Estimates are arithmetic. Any total you compute from /usage-pricing.json is a calculation on published rates, not a quote. A row with quote_above carries no price: the vendor sells above that volume by quote.

Caching and limits

The static feeds are cached at the edge for an hour. The three live DNS endpoints are limited per IP address and answer 429 with Retry-After when exceeded. If you need the whole corpus regularly, fetch /providers/core.json and filter locally rather than calling per provider.

Licence

The MCP server's code is MIT. The data these feeds serve is not part of that licence; it is published for reading, each figure attributed to its vendor page. For reuse beyond that, ask via the contact page.

On this page