Spec ≠ Documentation
Plain OpenAPI is a contract, not a story. You still need a separate docs site, separate diagrams and a separate try-it-out tool.
New · Hosted MCP for every published API
The Collaborative Platform for API Docs, Specs & AI-Ready APIs
VerJSON is where teams design, version and publish their APIs. Author OpenAPI 3.1 and the proprietary VerjsonAPI format with a rich docs renderer, sync with Crowdin, GitHub and Jira, and ship a public docs site with a built-in hosted MCP server – ready for AI agents on day one.
No credit card required • Free tier available • Deploy docs to your own domain
API Docs Are Stuck in the Past
Spec files are unreadable in Git, docs sites are disconnected from the source of truth, and nothing is built for the AI-agent era.
Drift Between Tools
Repos, translations, issue trackers and the published docs site fall out of sync the moment a single field changes.
Painful Collaboration
Editing big YAML files in branches makes parallel work risky. Reviews are line-by-line instead of meaningful change-by-change.
Not Ready for AI Agents
LLMs and copilots want machine-readable, callable APIs. Static docs sites can't expose your endpoints to an agent.
Proprietary format
Meet VerjsonAPI – OpenAPI, Supercharged
VerjsonAPI is a strict superset of OpenAPI 3.1. It stays fully exportable as standard OAS, but adds everything you actually need to ship great API docs – authored, versioned and rendered in one place.
Rich Docs Renderer
Auto-generated operation pages and object pages, with overviews, parameters, request bodies, responses, error tables and code samples – all themable to match your brand.
Markdown Pages & Embeds
Author guides, tutorials and reference articles in extended Markdown. Embed diagrams, callouts, content lists and live operation references with the document:// protocol.
Try-It-Out Console
Persistent, per-operation test suites. Save multiple example requests, manage authentication schemes, and execute requests directly from the docs site.
Authentication Schemes
Map OpenAPI security schemes to dynamic credential headers. Configure which credentials are usable in docs vs. MCP, with encrypted storage per published API.
Operation & Object Diagrams
Schemas turn into interactive JSON-tree, relation (ERD) and sequence diagrams automatically – exportable to SVG, PNG and PDF.
Themes & Branding
Per-document themes for the operations pane, method badges, cards and code samples, plus custom logos and color palettes for your published docs.
VerjsonAPI
OpenAPI 3.0 / 3.1
JSON Schema
Sequence Diagrams
JSON Tree Diagrams
Relation (ERD) Diagrams
Manifest Sites
Markdown
Hosted publishing
Publish Once. Get Docs, an API and an MCP Server.
Hit publish on any VerjsonAPI document and VerJSON gives you a complete, hosted developer surface – a docs site, a downloadable spec, a JSON API and a hosted MCP endpoint that AI agents can connect to instantly.
Hosted MCP – Plug & Play
Every published API automatically exposes a Model Context Protocol server at
docs.verjson.dev. Point Claude, Cursor or any MCP-compatible client at it and they can
discover operations, read schemas and call your API – with the credentials you choose to allow.
Public Docs on a Named Path
Publish to docs.verjson.dev/your-api or attach a verified custom domain. Docs include the renderer, search, try-it-out and downloads – no separate site to maintain.
Spec & Snapshot Downloads
Each published version exposes the OpenAPI spec, a portable VerjsonAPI snapshot and JSON exports for downstream tooling and code generation.
Per-API Credentials
Configure auth schemes per published API. Choose which credentials end users can use in docs and which are exposed to MCP – stored encrypted, never bundled into the page.
Versioned REST API
A clean /v1 REST API with cursor pagination, RFC 7807 errors and scoped API keys for documents, renderings, publishing and more – ideal for CI/CD. See the API Docs →
Manifest Sites
Combine multiple APIs, guides and diagrams into a single navigable docs site with the manifest format, including search, breadcrumbs and infinite scroll.
Integrations
Streamline Publishing with Crowdin, GitHub & Jira
VerJSON plugs into the tools your team already uses, so docs, translations and release notes stay aligned with every API change.
Crowdin
Push API descriptions, Markdown pages and operation summaries to Crowdin, then pull translated copies back into per-language documents. Optionally split by file paths for big specs and keep localized docs continuously in sync.
- Workspace-level API token, encrypted at rest
- Per-document project, file and split settings
- One-click publish of translated documentation
GitHub
Link any document to a file in a GitHub repository. Pull the latest version into VerJSON, edit collaboratively, then commit changes back to the branch – with commit and file SHAs tracked per version for clean diffs.
- PAT-based connection per workspace
- Two-way sync with branch and path tracking
- Perfect for spec-as-code repositories
Jira
Tie API releases to your Jira project. Attach issue keys, link to a Jira version and auto-generate release notes from the changes between two versions of your spec – a complete, auditable trail from ticket to published API.
- Site URL + API token configured per workspace
- Release notes with linked issues and Jira versions
- One source of truth across product and platform teams
Everything Your API Workflow Needs
Beyond authoring and publishing, VerJSON gives you the editor, versioning and visualization tools API teams have been bolting together for years.
Visual Structure Editor
Tree-based editor for OpenAPI and JSON Schema with $ref resolution, fixed-typing constraints, scoped search and a full Monaco fallback for power users.
Real-Time Collaboration
CRDT-based editing via Yjs. Multiple people edit the same document live, with presence, cursors and automatic conflict-free merging.
Semantic Versioning & Diffs
Every change becomes a version with major.minor.patch numbering and a JSON Patch (RFC 6902) diff. Compare any two versions side by side.
Automatic Diagrams
Schema, sequence and relation (ERD) diagrams generated from your specs. Themable, exportable and embeddable directly into Markdown pages.
QA & Consistency Checks
Detect missing types, breaking changes and structural inconsistencies before publishing. Catch regressions early in the pipeline.
Workspaces & Permissions
Workspace and document-level roles (owner, editor, publisher, viewer) with invitations, notifications and per-document PIN protection.
Built for Technical Teams
OpenAPI 3.0 & 3.1 + VerjsonAPI extension
Hosted MCP server for every published API
Custom domains for published docs
Crowdin, GitHub & Jira integrations
Try-it-out console with persistent test suites
JSON Schema draft-07 and later validation
$ref resolution and sideloaded schemas
Sequence, JSON-tree and relation (ERD) diagrams
Manifest-driven multi-API documentation sites
Markdown with embeds, content lists and PDF export
Diagram exports to SVG, PNG and PDF with watermarks
Workspaces with role-based permissions
Document PIN protection & access logs
Versioned
/v1 REST API with scoped keysImport from URL with authentication support
Undo/redo with full version history
Who Uses VerJSON
API Product Teams
Design, version and ship APIs as first-class products with branded docs, MCP and customer-facing try-it-out – all from the same source of truth.
Developer Experience
Replace fragmented docs stacks with one platform. Localize via Crowdin, embed diagrams and tutorials, and expose AI-ready endpoints automatically.
Platform & Architecture
Manage many APIs across services with manifests, ERDs and sequence diagrams. Track structural changes and breaking modifications between versions.
AI & Agent Builders
Plug agents into any VerJSON-published API via the hosted MCP server – no glue code, no extra hosting, with fine-grained credential control.
Frequently Asked Questions
What is VerjsonAPI?
VerjsonAPI is VerJSON's proprietary extension of OpenAPI 3.1. It keeps full OAS compatibility but layers on rich Markdown documentation pages, embedded diagrams, persistent try-it-out test suites, theming, and a built-in renderer that turns your spec into a polished documentation site.
What is the hosted MCP and how does it work?
Every API documentation site published through VerJSON automatically gets a plug-and-play MCP (Model Context Protocol) server hosted at docs.verjson.dev. AI agents like Claude or Cursor can connect to it directly to discover operations, read schemas and call your API, with credential exposure controlled per published API.
How do the Crowdin, GitHub and Jira integrations work?
Crowdin keeps translated copies of API documentation in sync with the source spec. GitHub links a document to a file in a repository so changes can be pulled and pushed in either direction. Jira lets you attach issue keys to release notes and link versions to Jira releases, providing a complete change-management trail.
What file formats does VerJSON support?
OpenAPI 3.x, the proprietary VerjsonAPI extension, JSON Schema, sequence diagrams, JSON-tree and relation (ERD) diagrams, navigation manifests, and Markdown documentation with extended syntax including tables, task lists, embedded diagrams and content directives.
Where can I publish my docs?
Published documents are served from a named path on docs.verjson.dev (for example docs.verjson.dev/your-api) and can be mapped to a verified custom domain. Each published API gets a docs site, an OpenAPI spec download, a hosted MCP endpoint and configurable authentication.
How does real-time collaboration work?
VerJSON uses Yjs, a CRDT-based framework, for real-time collaborative editing. Multiple users can edit the same document simultaneously with automatic conflict resolution, live cursors and presence indicators.
Does VerJSON have an API for automation?
Yes. VerJSON exposes a versioned REST API at /v1 for managing documents, versions, renderings and publishing, with scoped API keys for CI/CD pipelines and external automation.
Ship Better API Docs – and an MCP Server – Today
Join teams using VerJSON to author, version and publish APIs that humans and AI agents can use on day one.