Expose the OpenAPI spec download in the contextual menu - #315
Merged
Conversation
API reference pages are generated from the hosted spec, but the contextual menu had no route to the spec itself. download-spec only renders on API reference pages, so it costs nothing elsewhere. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
kylegani
marked this pull request as ready for review
August 12, 2026 14:43
yaseenisolated
approved these changes
Aug 12, 2026
jonoirwinrsa
approved these changes
Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
download-spectocontextual.options, placed aftercopy/viewso the "fetch the raw artifact" actions group together (array order controls menu order).Why
Our API reference is generated from a hosted spec (
navigation.versions[0].tabs[4].openapi.source->https://s3.eu-west-1.amazonaws.com/www.cerebrium.ai/openapi_spec.json, public, 71 paths, 349 KB), and pages like/docs/api-reference/apps/list-appsare live. Until now the contextual menu offered no route to the spec itself, so an agent on an API page could read one endpoint's prose but not pick up the machine-readable contract.Per https://www.mintlify.com/docs/ai/contextual-menu,
download-spec"Downloads your deployment's OpenAPI spec" and only appears on API reference pages, so this is inert on the other 52 pages.Validation
docs.jsonvalidated against Mintlify's published schema (https://mintlify.com/docs.json, fetched live):anyOfartifact, the theme union reporting'maple' was expectedetc. because our theme ismint.mintbranch specifically: 1 error on both base and this branch, identical (Additional properties are not allowed ('css' was unexpected), a pre-existing real Mintlify feature their published schema has not caught up to).Net: zero new schema errors, and
download-specpasses thecontextual.optionsenum.Not included
Also valid but deliberately left out:
grok,aistudio,devin,devin-desktop,devin-mcp(worth adding only if those are target agents) anddownload-pdf(Enterprise plans only).