<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/93eb5cd949e4453b9f6d48d6db0d4fe5&quot; frameborder=&quot;0&quot; width=&quot;3024&quot; height=&quot;2268&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2268</height><width>3024</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2268</thumbnail_height><thumbnail_width>3024</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/93eb5cd949e4453b9f6d48d6db0d4fe5-d2c605d39409ef8b.gif</thumbnail_url><duration>125.256</duration><title>Patchbay Turns API Changes Into Tested Pull Requests</title><description>This Loom explains Patchbay’s approach to reducing API downtime caused by unnoticed API changes. It cites that over 30% of downtime came from API changes nobody noticed, and notes that “nobody reads changelogs” so each team edits its own code. The speaker demonstrates turning a published API spec change into an agent-readable feed that lets an agent find the affected code in sample REPLs, write fixes, and test them in a clean VM, retrying from a snapshot if tests fail. Developers then receive pull requests with differences in test results to merge, and the same feed can be used by any coding agent, with providers like Stripe envisioned as a next step.</description></oembed>