The published validator OpenAPI document lives at ../openapi/validate.openapi.json.
If you need smaller machine-readable route and envelope-family maps instead of the full OpenAPI document, also inspect ../references/validator-routes.json, ../references/validator-envelope-families.json, and the TypeScript convenience layers ../projections/typescript/validator-routes.ts and ../projections/typescript/validator-envelope-families.ts. The compact route layer now carries auth posture, bounded query-parameter metadata, and response-status-to-envelope mappings, but OpenAPI remains the stronger source for full route semantics. That stronger-source boundary is enforced directly by ../scripts/check-openapi-coherence.js, not only by the broader reference-pack verifier.
The current OpenAPI surface documents the validator HTTP family:
POST /api/validatePOST /api/validate/batchPOST /api/validate/fixGET /api/validate/statsGET /api/validate/gates
OpenAPI makes the validator boundary easier to consume from outside the full application repository. It also gives reviewers a machine-readable contract instead of forcing them to infer request and response shapes from prose alone.
Use these when you want sample envelopes instead of just schema-level contract data:
Use these when you want to read the strongest published route contract directly instead of reconstructing behavior from compact summaries:
../examples/client/ts-openapi-route-summary.tsopenapi-codegen-recipes.md../examples/client/cjs-package-openapi-reference.cjs../examples/client/esm-package-openapi-reference.mjs../examples/client/ts-package-openapi-reference.ts../examples/client/python-openapi-reference.py
These recipes prove that consumers can inspect the published OpenAPI document directly from a repo checkout, a packed package artifact, or an extracted package tree to recover the validator route family, bearer-auth posture, bounded stats query metadata, and response-status coverage without depending on private runtime code or immediately dropping to the compact route map first. If you want generator-oriented output instead of route inspection, use openapi-codegen-recipes.md for the openapi-typescript path across repo-local, CommonJS, ESM, and TypeScript package-consumer styles.
The OpenAPI document is a projection artifact from the live validator surface. The validator implementation remains the stronger source of truth for fine-grained runtime behavior.