Ship
Ship is what happens after a version is ready: publishing it, planning its sunset, exporting it in another format, generating an SDK and trying it against a mock.
The usual order is cut a version, publish it, then manage it on Published and plan its end of life on the Sunset timeline. Convert it with the Export studio (what survives is in Understand export fidelity), brand its SDK in SDK settings, and try its mock with Mock try-out. The guides behind the mock engine are under Mock runtime.
Cut a version
Create a new revision of a project to edit and later publish.
Publish a version
Freeze a version and make it available to browse, export and MCP.
Published
Every published version, with its visibility, access URL and hosted mock.
Sunset timeline
When each deprecated version reaches end of life, by project, with CSV export.
Browse published specs
Find and read published versions, public or behind an API key.
Export studio
Pick a target format, verify what converts, then generate and download it.
Export a spec
Download a published version as OpenAPI, Arazzo or JSON Schema.
Understand export fidelity
See what an export preserves, changes or loses, and why, before generating.
SDK settings
Name and brand generated SDK packages, and offer a public Get SDK download.
Mock try-out
Try a mock first — preview a response, call it, or test-drive an export.