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