Documentation

How Repairo works

Connect GitHub, track OpenAPI before → after, map TypeScript impact, open a Dependabot-style repair PR.

Quick start

Repairo is the application layer between API contracts and customer codebases — the self-maintaining APIs loop: detect → impact → apply as a PR.

  1. Sign in to the dashboard to authenticate with your repository:Sign in with GitHubRequires repo and read:user scopes.
  2. Use Try your repo or create a watched integration with before/after OpenAPI paths (or the same path on two refs).
  3. List TypeScript consumer file paths that call the API.
  4. Run repair → review the blast radius → open a PR on GitHub.
No OpenAPI repo handy?Try the Fixture Demo

Automated Integrations (Pro/Business)

Instead of manually uploading specs, you can configure Repairo to poll remote OpenAPI schemas (like Stripe or internal microservices) continuously in the background.

  • Scheduled daily polling or real-time Webhook triggers
  • Automatic discovery of TypeScript/TSX consumer files across your repository
  • Zero-touch PR generation when upstream breaking changes are detected

OpenAPI diffing

Repairo parses before and after OpenAPI documents, then classifies changes into breaking, additive, and safe categories — path/method moves, required fields, enum renames, base URL / version bumps, and status-code shifts.

The diff is the source of truth. We do not guess from runtime traffic or undocumented endpoints.

Impact mapping

For each classified change, Repairo traces TypeScript call sites, types, and status checks in the consumer files you list. Output is a blast-radius summary: which files and symbols are likely affected.

  • Supported today: TypeScript / TSX consumer sources
  • You provide explicit file paths (no whole-monorepo crawl yet)
  • Impact is advisory — always review before merge

Deterministic transforms

Patches are rule-based, not free-form LLM rewrites. Supported safe transforms include:

  • URL / version path bumps (e.g. /v1 → /v2)
  • Required field additions where a default is unambiguous
  • Enum rename updates in string literals and unions
  • Status-code expectation updates in checks

Each run includes a safety score. Unsupported or ambiguous changes are left for humans — Repairo will not invent business logic.

GitHub permissions

OAuth scopes: repo (read specs + open PRs) and read:user (identity). See Security for storage and architecture.

Plans & limits

  • Free: 1 repository, manual/on-demand scans, manual fixes.
  • Pro ($29/mo): Up to 10 repositories, scheduled daily scans, automated fix PRs.
  • Business ($99/mo): Up to 50 repositories, real-time webhooks, auto-merge capabilities.
  • Enterprise: Unlimited repositories, VPC/Self-hosted, SSO.

Full comparison on Pricing.

Try on your GitHub repo