OpenAPI Spec to Contract

[KingSora]

Good day :)

I'm new to oRPC but I'm already really impressed with the project and its architecture.
I have 3 main usecases for oRPC:

• Within a monorepo where I can share code / types between client and server. (contract)
• As documentation (swagger / openapi)
• From within "3rd party clients" which only have the openapi.json file(s).

The workflow for the first two usecases was pretty clear, but the third one is only possible via Hey-API from what I have been reading. (Please correct me if I'm wrong)

So my question / thought would be whether it is / would be possible to create a contract out of the openapi.json file? As far as I understood the whole architecture, the contract is a superset of the whole openapi.json file. zod v4 also supports conversion between JSONSchema, so validation shouldn't be problem there. Am I missing something is this openapi.json -> contract a valid approach?

There is also the functionality to write the contract as a json file, but there I don't have any validation. Maybe supporting contract.json files which have the validation part would also be enough to generate a full fledged client out of it?

[dinwwwh]

Did you try this? https://orpc.dev/docs/advanced/publish-client-to-npm