API registry for OpenAPI and AsyncAPI
Keep every OpenAPI and AsyncAPI document your company publishes in one versioned API registry, and power docs, SDKs, and MCP servers from it.
Scalar Registry stores, versions, and manages OpenAPI and AsyncAPI documents, JSON Schema, and Spectral rules in one source of truth with a deep Git integration.
Why teams put their APIs in Scalar
- One document, every interface. A single API document in Registry feeds your API documentation, SDKs, and hosted MCP servers, so they cannot drift apart.
- Built on open standards and open source. Scalar's API tooling is developed in the open at github.com/scalar/scalar, with 15.7k GitHub stars. The API reference that renders your registry documents is documented on Microsoft Learn and is the default docs UI in eight frameworks.
- Used by teams that run many APIs. Companies such as Thomson Reuters, Lufthansa, and PAR publish developer portals with Scalar; see customers.
Publish from the command line or CI
Registry fits the way API descriptions are already produced. Push a document with one CLI command, scalar registry publish ./openapi.yaml --namespace your-team --slug your-api, or wire the same step into GitHub Actions or GitLab CI/CD so every merge publishes a new version. The command is the same for OpenAPI and AsyncAPI documents. Prefer clicking? Upload in the dashboard instead.
Governance with Spectral rules
Store Spectral-compatible rules in Registry and lint every document against the same ruleset, locally with scalar document lint or in CI before a change is published. Shared JSON Schema objects live next to the APIs that reference them, so common models are defined once.
Where your OpenAPI documents come from
Many teams generate their OpenAPI document from code. The framework guides for .NET, FastAPI, and NestJS show how, and the learn hub covers OpenAPI itself. Every plan includes Registry; plans differ in how many APIs you can publish (3 on Free, 15 on Pro, 25 on Business, unlimited on Enterprise). Start free or book a demo.
Why a Registry?
Managing APIs can get messy fast. Teams need to know where the source of truth lives, how versions are managed, who has access, and how downstream consumers discover updates.
Registry gives your team a central place for OpenAPI and AsyncAPI documents and the workflows around them. Once an API document is in Registry, you can power docs, SDKs, publishing, and automation from the same source.
Create docs and SDKs
Create API docs from Registry with just a few clicks. Your docs stay connected to OpenAPI changes, so updates move from source to published documentation without copy-paste work.
Generate SDKs from the same OpenAPI documents. Keep client libraries aligned with API changes while Registry handles the connection between the source document and the generated tooling.
Features
Keep API documents, schemas, and rules in one managed place.
Connect Registry to repository workflows so updates can follow your existing review process.
Version and publish OpenAPI and AsyncAPI documents used by docs, SDKs, and automation.
Manage shared schemas alongside the API documents that depend on them.
Store rules for consistent API governance and validation workflows.
Control whether API documents are internal, shared with a team, or public.
Ready to manage your APIs?
Follow the Getting Started guide to create an account and upload your first API document.
Frequently asked questions
What is an API registry?
An API registry is the central, versioned store for your API descriptions. Instead of OpenAPI files scattered across repositories and wikis, every team publishes to one place, and docs, SDKs, and other tools read from it.
Does Scalar Registry support AsyncAPI?
Yes. Registry stores and publishes AsyncAPI documents the same way as OpenAPI. scalar document lint also lints AsyncAPI with Spectral's AsyncAPI ruleset; scalar document validate is OpenAPI-only today.
How do I publish an OpenAPI document to the registry?
Run scalar registry publish ./openapi.yaml --namespace your-team --slug your-api with the Scalar CLI, use the GitHub Actions or GitLab CI/CD examples, or upload the file in the dashboard.
Can I keep API documents private?
Yes. You control whether each API document is internal, shared with a team, or public, and the CLI can publish a version as private.
Can I lint API documents with my own rules?
Yes. Store Spectral-compatible rulesets in Registry and reference them with scalar document lint --rule, locally or in CI. See rules.
Is Registry free?
Registry is part of every plan, including Free. The Free plan covers up to 3 APIs, and larger plans raise that limit. See pricing.
Related
- Learn: What is OpenAPI? · API catalog
- Docs: Publish with the CLI
- Product: SDK generator — generate typed clients from the documents in your registry
