Y Combinator's Requests for Startups · Fall 2026

Self-Maintaining APIs

Requested by Harsha Gaddipati · View in YC · Start with an MVP

Build a production-ready platform that keeps customer codebases automatically in sync with the APIs they depend on — detecting and fixing breaking changes and adopting new features, like Dependabot for API behavior. Core vision: When an API provider ships a breaking change or a new capability, every customer scrambles to update. Build the infrastructure that connects providers to customer codebases and automatically detects breaking changes and feature launches, then generates the fixes. It can operate as a per-provider agent or as a neutral third-party tracking changes across many vendors. The system must support the full sync loop: 1. Connect a customer repo and the API providers it uses 2. Track each provider's API for breaking changes and new features 3. Detect where the customer's code is affected 4. Generate fix pull requests automatically 5. Let the customer review, test, and merge with confidence Core capabilities: Connections and tracking: - Connect a code repository (represented via repo integration) - Register API providers/vendors the codebase depends on - Track API versions, changelogs, and specs for changes (via a change-detection layer) - Support both per-provider mode and neutral cross-vendor mode Change detection: - Detect breaking changes and map them to affected code paths - Detect newly launched features worth adopting - Severity and impact scoring per change - Clear, human-readable explanation of each change Automated fixes: - Auto-generate pull requests that apply the necessary code changes (via a patch-generation layer) - Include tests or verification steps where possible - Group related changes and explain the diff - Safe rollback and opt-out per change Dashboard and control: - Overview of all connected repos and their sync status - A feed of detected changes and generated PRs - Alerts for high-severity breaking changes - Metrics on time saved and changes handled Design: Developer-first and precise — a clean dashboard with clear diffs, PR-centric workflows, and strong signaling of severity. It should feel like trustworthy infrastructure engineers are happy to hand the keys to.

Builds a working MVP of a platform that keeps customer codebases in sync with API changes. Includes connecting a repo and an API provider, detecting breaking changes and new features, auto-generating fix PRs, and a dashboard tracking affected repos. Deep code transformation is represented via a change-detection and patch-generation layer.