Self-Maintaining APIs
The speaker argues that API communication is fundamentally broken across the industry, with breaking changes and new features going unnoticed. Since agentic coding tools have proven viable and developers accept external tool access to codebases, API providers should automatically apply changes to customer code rather than just announcing them—similar to how Dependabot works for dependencies.
Summary
The speaker presents a critical analysis of API communication failures based on experience working with over 50 API vendors, including early-stage startups and AWS. The core problem is that breaking changes ship with insufficient warning, useful features launch quietly without awareness, and changelogs go unread. This friction results in significant costs—the speaker cites that over 30% of service downtime at AWS was attributed to unnoticed external API and package changes.
The speaker argues this problem persisted because the infrastructure for automated code changes didn't exist. However, agentic coding tools like Claude, Davenin, and Gravile have fundamentally changed this landscape. Two years ago, developers would never grant external tools access to their codebases, but this is now standard practice, proving both developers and enterprises value these tools sufficiently to accept the security model.
The proposed solution is for API providers to move beyond passive communication to active code modification. When Stripe ships a breaking change or new feature, for example, an agent should automatically scan customer codebases, identify affected usages, and open pull requests with fixes. This could be implemented either as per-provider agents (like a Stripe Update Agent) or as a neutral third-party service tracking changes across multiple vendors—essentially Dependabot for APIs rather than just dependencies.
Key Insights
- Over 30% of service downtime at AWS was caused by external APIs and package changes going unnoticed, demonstrating the severity of the API communication problem even at large enterprises.
- Developers and enterprises have proven willing to grant codebase access to external agentic tools, a paradigm shift from two years ago when this was considered unthinkable.
- The infrastructure for automated code changes already exists; what is missing is the application layer connecting API providers to customer codebases.
- API providers should transition from announcing changes to actively applying fixes, with agents automatically scanning codebases and opening pull requests when changes are released.
- This solution could be implemented either as per-provider agents or as a neutral third-party service—essentially creating Dependabot-like functionality for APIs across vendors.
Topics
Transcript
[0:00] Over the past year, I've worked at over 50 API vendors, mostly early stage startups, and just one pattern is consistent. API communication is broken. Breaking changes ship with little warning. Useful features quietly launch and go unnoticed. Change logs don't get read. Heck, this is a problem even when I worked at AWS. Over 30% of a service downtime was due to external APIs and package [music] changes going unnoticed. This friction made sense before agentic coding tools existed. However, now it doesn't. Agentic coding tools like cloud code, davenin, [music] gravile, etc. [0:30] prove that developers and enterprises are willing to give codebase access to external tools provided they're valuable. Two years ago, this was unthinkable, but…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Y Combinator
Why Inference Matters 12x More Than Training | YC Paper Club
This YC Paper Club event features five AI inference experts discussing why inference matters 12x more than training and how to optimize LLM serving at scale. Speakers cover kernel optimization, parallelism strategies, quantization, routing across providers, compiler design, and emerging inference engine architectures for handling complex agent workloads.
A Different Approach To Launch Videos
Farza Majeed shares his unconventional approach to product launches, emphasizing constant "demo-driven" content creation on algorithmic platforms rather than expensive, one-time launch events. He demonstrates how authentic, frequent videos with strong hooks and compelling narratives drive user acquisition more effectively than polished productions, supported by concrete metrics showing conversion rates across platforms.
Magic Patterns CEO Reviews Startup Websites
The episode features Alex Danalovich, CEO of Magic Patterns, discussing the origin and functionality of their AI design tool tailored for non-designers. The conversation also includes critiques of various startup websites, emphasizing the importance of clear communication and user-centric design.
AI Safety Fact vs. Fiction | YC Paper Club
A YC AI Safety Club event featuring François Bonneau, Clark Barrett, and Michael Kogut discussing the distinction between AI safety hysteria and scientific facts. The speakers advocate for engineering-based safety approaches through formal verification, adaptive stress testing, and industry best practices rather than focusing on speculative extinction scenarios.
Demis Hassabis: Put your life force into a problem that matters
Demis Hassabis argues that pursuing difficult, impactful problems is worthwhile given life's finite time and energy. He emphasizes the importance of interdisciplinary work and deep tech development, while advocating for building systems that account for AGI arrival around 2030 by using modular, specialized tools rather than monolithic general-purpose systems.