14,400 public APIs already have their docs on Skmtc
A page for every operation, a diff each time the API changes, and Markdown that ChatGPT, Claude and your own tools can read. Drop the file and sign in with GitHub.
Sign in with GitHub to finish. Your docs stay private until you make them public.
Your schema goes into the same catalog that tracks thousands of public APIs, so your docs get everything they get.
Each change is listed with its severity, on the API and on every operation it touches. Readers can follow them in Atom or JSON Feed.
Every page has a Markdown copy and the API has an llms.txt. ChatGPT, Claude and Gemini can also search and read it through the Skmtc MCP server.
Readers ask in plain words on any docs page. Each answer links the operations and schemas it used, so they can check it.
Generate a TypeScript client next to the docs, or set up a pipeline that opens a pull request in your repository when the API changes.
Pick the way that suits how you ship. Every new version gets its own diff.
Give us the address of the file in your repository or on your site. When it changes, a new version appears.
One step in GitHub Actions or one REST call with a token. The docs change when your code does.
Attach the schema and ask for docs. The Skmtc app signs you in with GitHub and replies with the link.
Drop the schema anywhere on this page, or choose it.