Getting started

SKMTC turns OpenAPI schemas into live, searchable API documentation. Your coding agent can find an API, read its operations through MCP, or fetch the same docs as compact Markdown. When you publish a new schema revision, the docs track it. Code generation for published APIs is coming soon.

You can explore public APIs without an account. To publish your own schema, sign up with GitHub. Your first sign-in creates a personal account; an organization is optional.

To publish without an agent, open Your APIs, select New API, and upload an OpenAPI JSON or YAML file. Check the account and slug before selecting Add API. The browser form starts at Private.

Point your agent at SKMTCCopy Anchor Link

Paste this into Claude Code or another coding agent. Replace the example account and slug when you know them. The agent should inspect your repository before suggesting a schema file.

Read https://docs.skmtc.dev/docs/getting-started.md and
https://docs.skmtc.dev/docs/getting-started/publish-api.md. Help me publish
the OpenAPI schema in this repository to SKMTC. Find the schema file, then show
me the destination account, API slug, and visibility (private or public) and
ask me to confirm all three before sending anything. Treat private as a normal
choice; do not assume public. Explain how to create a publish:schemas token and
use SKMTC_TOKEN from my environment without printing or committing it. Use the
REST API for a local file or the SKMTC MCP publishing tool when configured.
After publishing, give me the API page and its Markdown URL. If the schema is
generated in CI, use the CI guide at
https://docs.skmtc.dev/docs/getting-started/publish-from-ci.md.

The documentation URLs above also serve plain Markdown, so an agent can read them without rendering the website. Public API pages have the same option: append .md to an API or operation URL, or request Accept: text/markdown from its HTML URL. An API's llms.txt lists its operations for an agent to navigate.

Authenticate to publishCopy Anchor Link

Open Settings → Access tokens, choose Generate new token, name it, set an expiration, and select publish:schemas. Copy the secret when it appears; it is shown only once. Save it as SKMTC_TOKEN in your environment or CI secret store. A personal token can publish to your account, or to an organization where you are a member. Publishing through REST or MCP uses that token; a browser session does not authenticate either interface. Public discovery through MCP and Markdown does not require a token.

Hello world: publish a private APICopy Anchor Link

Save this as openapi.yaml:

openapi: 3.1.0
info:
  title: Hello world
  version: 1.0.0
paths:
  /hello:
    get:
      operationId: getHello
      summary: Say hello
      responses:
        '200':
          description: A greeting
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string

Choose your destination explicitly before sending:

Account:    ada
API slug:   hello-world
Visibility: private

Replace ada with your SKMTC account handle. Set SKMTC_TOKEN to the token you just created, then run:

curl --fail-with-body \
  --request POST \
  --header "Authorization: Bearer $SKMTC_TOKEN" \
  --header 'Content-Type: application/octet-stream' \
  --data-binary @openapi.yaml \
  'https://api.skmtc.dev/v1/apis/publish?owner=ada&slug=hello-world&visibility=private&filename=openapi.yaml'

Open https://skmtc.dev/ada/apis/hello-world while signed in. The public Markdown convention is https://skmtc.dev/ada/apis/hello-world.md; a private API stays private, including its Markdown view. See Publish an API for Claude Code MCP setup, revisions, and visibility rules, or Publish from CI for automation.