orpc-openapi

Attach openapi metadata from @orpc/openapi to each procedure, setting method, path, and successStatus, then serve the router with OpenAPIHandler from an adapter subpath like @orpc/openapi/fetch. Path params use {id} syntax matching required input schema fields.

Use OpenAPIGenerator from @orpc/openapi with a schema converter such as ZodToJsonSchemaConverter, calling generate with your router and a base document containing info and servers. It produces OpenAPI 3.2 by default and accepts a version option for 3.1 or 3.0.

Yes, both handlers accept the same router. Mount them on different prefixes such as /api and /rpc, try each handler in turn, and return the first response whose matched flag is true.

Query, path, and form values always arrive as strings over HTTP. Add SmartCoercionHandlerPlugin from @orpc/json-schema with your schema converters to perform lossless coercions like '123' to 123 or ISO strings to Date.

Bracket notation cannot represent empty objects or arrays, root-level arrays, or objects whose keys are all numbers. Repeated keys and color[]= syntax build arrays, while [key] builds nested objects, and all values remain strings.

Use orpc-contract for contract-first workflows: defining contracts with oc from @orpc/contract, implementing them with implement, shipping minified JSON contracts, or generating a contract from an existing OpenAPI spec. Use orpc-openapi for serving and documenting the REST side.