Serve raw openapi json spec as part of fern docs

[paul-paliychuk]

Feature Description

We would like to be able to expose our openapi.json file to the people using our docs.

Use Case

We've had requests by the community for the openapi file so that they could generate their own sdks using the tooling of their choise, particularly for languages/ecosystems we currently do not support (or that we do not intend to support in the future).

Proposed Experience (Optional)

Just the JSON file served on the api-reference/json endpoint.

Alternatives Considered (Optional)

We are currently considering open sourcing our fern docs repository to make the openapi file available to the public.

[dannysheridan]

Thanks for filing. I could see us exposing the OpenAPI specification(s) at one of the following:

• https://help.getzep.com/api-reference/openapi
• https://help.getzep.com/openapi
• https://help.getzep.com/.well-known/openapi.json # or .yml/.yaml [but what happens when you have multiple specs?]

ReadMe takes the approach of sharing a link to each OpenAPI spec you've uploaded on the /openapi url: https://developer.bill.com/openapi