API Scope

Use this page when you need a precise statement of what PatchPatrol publicly documents today and where that boundary stops.

Source of truth: this page is derived from shipped PatchPatrol contracts and the checked-in public docs boundary for the current product surface.

PatchPatrol does not currently publish a broader first-party public SaaS HTTP API contract. The checked-in public surface today is the CLI plus the documented GitLab-based review workflow and provider posture.

What is public today

The public, source-backed material today is:

• The CLI reference for the shipped ai-review run and ai-review test commands.
• The configuration reference for the supported environment-variable contract and defaults.
• The advanced configuration page for operator-tuning and explicit compatibility controls.
• The policy controls page for the recommended artifact-first posture and supported delivery tradeoffs.
• Public guidance about OpenAI-compatible provider posture, which describes supported endpoint classes PatchPatrol can call rather than a PatchPatrol-hosted endpoint catalog.

What is not published yet

PatchPatrol does not currently publish generated or endpoint-by-endpoint SaaS API reference for its own service surface.

That kind of material requires a checked-in public contract such as an OpenAPI spec or equivalent source that is explicitly intended for external consumers.

Until that contract exists, this docs surface stays precise on purpose: it documents the shipped CLI and workflow behavior, not a broader endpoint catalog.

OpenAI-compatible Boundary

OpenAI-compatible docs describe which external endpoint classes PatchPatrol supports for provider calls and what compatibility contract they must satisfy.

They do not describe a broader PatchPatrol SaaS endpoint catalog, and they should not be read as a promise of first-party HTTP routes beyond what is publicly documented here.

Return to Reference.