Skip to content
Back to the registry

Publish your API on the public registry

Your OpenAPI spec is already in a repository. Point Spec0 at it and it becomes documentation anyone can read, a changelog anyone can follow, and a contract their agents can query — without you maintaining a docs site.

Free for your first three APIs. No workflow file, no secrets in your repo.

Four steps, about five minutes

  1. Step 1

    Connect your repository

    Install the Spec0 GitHub App on the repo your OpenAPI spec already lives in. Read-only, and scoped to the repositories you pick — not your whole account.

  2. Step 2

    Point at the spec file

    Spec0 finds the candidate specs in the repo; you confirm which file and which branch it should treat as the source of truth. Browse the tree if it is somewhere unusual.

  3. Step 3

    Choose public, and check the address

    You see exactly what public means and the URL the listing will live at — /registry/your-org/your-api — before anything is created, not after.

  4. Step 4

    Publish

    The spec is published, rendered as interactive documentation, and added to the directory. It is readable immediately, by anyone, with no account.

What a listing gets you

  • Interactive documentation with a schema explorer and code samples
  • A changelog computed from your specs, deep-linkable by version
  • Every version kept and downloadable as YAML or JSON
  • Readable by AI agents over MCP, and indexed by search engines
  • Lint and breaking-change checks on every pull request that touches the spec

Worth knowing first

Publishing a new version is a step you take
Spec0 checks pull requests automatically, but it does not publish a new version when you merge. You publish again from the dashboard, or from your own CI with the CLI.
Public means public
Anyone can read the spec, the changelog and the version history without an account. You can unlist a listing later, but anything already downloaded stays downloaded.
Your URL comes from your organisation name
Listings live at /registry/your-org/your-api. You see the exact address before you publish, and support can change it if it is not the one you want.
Only organisation admins can publish
Connecting a repository and publishing publicly are both admin actions, so a listing is never a surprise to the rest of your team.

Ready when you are

You will be asked to sign in. Publishing is an organisation-admin action, so bring the account that administers your Spec0 organisation.

Get startedRead the docs

Rather publish from your own pipeline? npm install -g @spec0/cli — CLI docs