OnPair

Documentation integrity

Your docs go stale one pull request at a time.

OnPair reviews every pull request for the documentation it leaves behind — the renamed env var, the changed route, the config key that no longer exists — and reports back as a GitHub check before the drift ships.

Get in

What changed

app/config/billing.ts
- retryLimit: 3,
+ retry: { limit: 3 },

What still says otherwise

docs/configuration.md:41

“Set retryLimit to control how many times a failed charge is retried.”

How it works

  1. A pull request opens

    OnPair reads the diff and identifies the contracts it touches — environment variables, routes, config keys, exported APIs.

    Changed files

    config/mail.ts +3 −1
start/env.ts +1 −1
docs/operations.md — untouched

  2. Docs are cross-checked

    It looks for places your documentation still describes the old behaviour, and judges how confident that match is.

    Still says otherwise

    docs/operations.md:18

    “Set MAIL_TRANSPORT to smtp to send for real.”

  3. A check run reports back

    Findings land on the pull request as a GitHub check, with a suggested update for each one. Acknowledge the ones that are fine.

    On the pull request

    1 blockingenvironment_variable · MAIL_TRANSPORT

What it catches

Each finding carries a severity and a confidence level, so a blocking contract change reads differently from a maybe.

Environment variables
A new or renamed variable that setup guides never mention.
MAIL_TRANSPORTBlocking
API routes
An endpoint whose path, method, or payload no longer matches the docs.
POST /billing/checkoutBlocking
Configuration keys
Config that changed shape while the reference stayed still.
retry.limitWarning
Public exports
A changed signature on something other people import.
SignInLinkService.issue()Warning
Documentation review
Prose that describes behaviour the change quietly replaced.
docs/operations.mdNote

Pricing

Priced on repositories and analyses, not seats.

Each analysis is a model call. Plans cap how many repositories OnPair watches and how many pull-request analyses run each month.

Starter

$1/month

A small team shipping on a handful of repositories. Enough analyses to review every pull request without treating OnPair as a background process.

Repositories
5
Analyses per month
750
Start with Starter
Recommended

Growth

$79/month

Several active repositories and a busier merge queue. The default for a team that wants every pull request read, not a sample of them.

Repositories
15
Analyses per month
3,000
Start with Growth

Scale

$199/month

A larger surface area — many repositories, many authors, no appetite for a cap getting in the way mid-sprint.

Repositories
50
Analyses per month
10,000
Start with Scale

Full pricing details