Use Reference for exact endpoints, schemas, and coverage. It is the stable contract view for builders.
26
OpenAPI-backed public API operations exposed from the v1 contract layer.
147
Reusable response and resource shapes that future SDKs and public docs can share.
7
Top-level capability groupings used across docs, reference, and future public repo packaging.
These tags mirror the contract taxonomy that can be published independently from private billing, CMS, and operator tooling.
Publish the contract layer, reference, docs, and SDK-facing artifacts. Keep payments, points, CMS, admin, and model strategy private.
Next surfaces
The future public repo should keep one contract source and multiple reading surfaces: docs for humans, reference for precise inspection, and OpenAPI for tooling.