About Repairo

API communication is broken. Breaking changes ship with little warning. Useful features quietly launch and go unnoticed. Changelogs don’t get read. At scale, unnoticed external API and package changes still drive a large share of production downtime.

That friction made sense before agentic coding tools. Developers and enterprises now routinely grant codebase access to tools that prove valuable. The infrastructure for automated code changes exists. What’s missing is the layer that connects API providers to their customers’ repos.

Repairo is a neutral third-party service — Dependabot for APIs. Track OpenAPI before → after, scan TypeScript consumers for affected usages, and open a PR with the fix. Providers shouldn’t just announce changes; with Repairo, those changes get applied as reviewable pull requests.

Today we ship deterministic transforms (URL bumps, required fields, enum renames) with a safety score — not opaque auto-merge. Human review stays in the loop.

Consumer engineering teams that integrate third-party or internal OpenAPI APIs, and platform groups who want contract drift fixed in git — payments, fintech, microservices, partner integrations. Per-vendor “install our update agent” is on the roadmap; the core loop works as a shared repair plane across vendors you watch.

This is the YC Requests for Startups problem space for Self-Maintaining APIs: connect contracts to codebases, identify impact, open the fix. We’re building it in public via Changelog, Docs, and a live demo.