MkDocs
MkDocs is a fast, simple, and beautiful static site generator designed for building project documentation from Markdown source files. Written in Python, it reads a single YAML configuration file (mkdocs.yml) and converts a directory of Markdown documents into a self-contained static HTML site. MkDocs supports multiple built-in themes (mkdocs, readthedocs), a rich plugin ecosystem via Python entry points, live-reloading development server, and one-command deployment to GitHub Pages.
MkDocs is profiled on the APIs.io network. Tagged areas include Documentation, Markdown, Open Source, Python, and Static Site Generator.
The MkDocs catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
MkDocs’ developer surface includes documentation, getting-started guide, GitHub presence, and 6 more developer resources.
Kin Score
Kin Score
How this is scored →scored 2026-09-25 · rubric v0.23.0
What adopting MkDocs moves on the Kin Score 5
MkDocs is an area vendor: providers adopt it to run part of their developer surface. This is the Kin Score checks its features can move for a provider that adopts it, what each one really earns, and what it earns nothing for.
MkDocs with Material for MkDocs gives a provider a self-hosted documentation site, a blog, and (through the community mkdocs-llmstxt plugin) an llms.txt that reads as the provider’s own because it is built from its pages on its domain. That is most of the realistic lift. The OpenAPI plugins render a reference page without a try-it console, the llms.txt plugin is in maintenance mode, Material’s own pages now promote Zensical, a new generator from the same team, and there is no MCP server, skills, agent card or well-known file in the ecosystem pages reviewed.
| Check | Earns | Through |
|---|---|---|
| Request/Response Examplespartial Agent ReadinessThe dimension reads examples inside the OpenAPI first; a rendered reference page reaches at most the Examples / Code Samples link fallback, and only if the provider declares it. |
1.8 of 7 | Neoteroi OpenAPI documentation plugin (community) |
| Documentationsaturated Developer Ergonomics95% of providers with a contract, docs and a reference already earn this; the vendor cannot move it for most of its buyers. |
4.0 of 4 | MkDocs static site generator |
| Publishes llms.txt DiscoverabilityBuilt from the provider’s own pages and served on the provider’s host, so it reads as the provider’s llms.txt. The plugin is in maintenance mode. |
4.0 of 4 | mkdocs-llmstxt (community) |
| API referencesaturated Developer Ergonomics94% of providers with a contract, docs and a reference already earn this; the vendor cannot move it for most of its buyers. |
3.0 of 3 | Neoteroi OpenAPI documentation plugin (community) |
| Blog Developer ErgonomicsPost to it and declare it as a Blog pointer. |
1.0 of 1 | Material for MkDocs blog plugin |
What MkDocs ships that earns nothing (2)
- Neoteroi OpenAPI documentation plugin (community) — The OpenAPI plugin renders documentation only; no try-it console is described, so there is nothing to declare as a Console.
- MkDocs static site generator — Nothing in MkDocs or the plugins reviewed serves an api-catalog, security.txt or protected-resource document.
A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership can. The rating is not for sale → · Full vendor facets artifact
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Mkdocs Context
JSON-LDSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
MkDocs API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions for this provider's data models.
MkDocs Configuration
JSON SCHEMAMkDocs Plugin
JSON SCHEMASecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.