Payment gateways & fintech APIs
When a processor bumps /v1 → /v2 or renames settlement enums, Repairo diffs the published OpenAPI, finds TypeScript checkout clients, and opens a PR with URL and enum updates — before card traffic fails.
Solutions
Use cases
Same engine — different places OpenAPI drift shows up.
Breaking changes in microservices
Internal producer services publish OpenAPI in the same monorepo or a contract repo. Point before/after at two refs (release tag → main), list consumer packages, and get a blast-radius PR for each dependent service.
Partner & third-party OpenAPI
Vendors ship new OpenAPI revisions on a schedule. Store before/after paths (or refs), watch the integration, and let webhook pushes trigger a repair run when the contract file changes.
Platform teams & API governance
Central platform groups use Repairo as a control plane: detect drift, enforce reviewable patches, and keep a run history of what changed and which PR landed — without mandating a sales-led rollout.
Requirements
You need an OpenAPI document in git and TypeScript consumers Repairo can read. Python-only or undocumented HTTP APIs are out of scope today — see Docs.