skmtc.dev valid

Skmtc

A public catalog of thousands of OpenAPI schemas with generated, browsable API docs, plus code generators and generator stacks that turn any schema into production TypeScript. When a schema changes, subscriptions turn the diff into a pull request against your repo.

For agents: Public catalog of thousands of OpenAPI schemas with generated API docs, TypeScript code generators, and PR automation for schema changes.

openapiapi documentationtypescript code generationopenapi schemaspull request automation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T06:37:06.922Z. Cached copy · Source on skmtc.dev

# Skmtc

> A public catalog of thousands of OpenAPI schemas with generated, browsable API docs, plus code generators and generator stacks that turn any schema into production TypeScript. When a schema changes, subscriptions turn the diff into a pull request against your repo.

## Read the markdown, not the HTML

Every API page on this site has a plain-markdown twin at the same URL with
`.md` appended, and every HTML page that has one says so in a
`Link: rel="alternate"; type="text/markdown"` response header. Sending
`Accept: text/markdown` to the HTML URL returns the markdown directly. An
operation's HTML page is ~150 KB; its markdown is ~5 KB of the same content.

An operation's URL is its path followed by its method, with parameters as
`:name`: `GET /repos/{owner}` lives at `docs/repos/:owner/get`. The
unversioned form resolves to the API's latest version and is the URL to cite;
every path prefix also answers with an `llms.txt` listing its operations and
narrower prefixes, so any endpoint is reachable by narrowing from the root.

- https://skmtc.dev/{account}/apis/{api}/llms.txt: every operation in an API, each linked to its markdown. Start here: one fetch replaces crawling hundreds of pages
- https://skmtc.dev/{account}/apis/{api}.md: what the API is, its license and source, operation counts by tag
- https://skmtc.dev/{account}/apis/{api}/docs/{path}/{method}.md: one operation at the latest version, with its parameters, request body and responses
- https://skmtc.dev/{account}/apis/{api}/docs/{prefix}/llms.txt: one node of the path tree, with its operations and narrower prefixes. Operation responses point at their parent node with `Link: rel="up"`
- https://skmtc.dev/{account}/apis/{api}/revisions/{version}/docs/{path}/{method}.md: the same operation pinned to one version
- https://skmtc.dev/{account}.md: one publisher, with every API they publish linked to its markdown
- https://skmtc.dev/explore.md: every public API in the catalog, one page at a time, each page linking the next. It also lists the categories
- https://skmtc.dev/explore/{category}.md: the same list for one category, such as /explore/payments-finance.md

Version-pinned URLs change rarely (`{version}` is a content hash) and are
served with a one-month shared TTL. Safe to cache, but not indefinitely: the
schema at that version is fixed, the rendering of it is not. The unversioned
form is served with a short revalidating TTL instead, so it tracks the latest
version closely.

## What changed

Poll one of these instead of re-crawling. Both are ordered by when skmtc-hub
RECORDED each entry, not by when it happened, so a fact recovered from an
older date still arrives at the top where a poller will see it. Each entry
carries both instants.

- https://skmtc.dev/feed.atom, /feed.json, /feed.md: catalog-wide revisions that broke something. Deliberately not every revision; the catalog records thousands on a busy day
- https://skmtc.dev/{account}/feed.atom, /feed.json, /feed.md: one publish
…

Related sites

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=skmtc.dev · GET /v1/domain/skmtc.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for skmtc.dev:
1. POST https://agentwebmap.com/v1/sites/skmtc.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://skmtc.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/skmtc.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/skmtc.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.