Okapi
AI agents that fix API breaking changes in your repos
Start new thread

Okapi - AI agents that fix API breaking changes in your repos

by
•
AI agents that fix API breaking changes in your repos. It is built for developers whose apps and agents depend on third-party APIs. These APIs change all the time, and one breaking change can take your app down in production. Okapi keeps your code up to date with every API it calls, so your app keeps working and your team stops chasing changelogs. Okapi works with any API and is 100% free.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt 👋, Today we're launching Okapi. Okapi's AI agents fix API breaking changes in your repos. The problem Your apps and agents call dozens of third-party APIs, and these APIs change all the time. Deprecation emails get lost, and nobody on the team owns the changelogs. Still, a small field change in an API response can take your whole app down in production. The solution Okapi keeps your code up to date with every API it calls, so your app keeps working. - Set it up in one click: connect your GitHub repo and you're done. - Stay ahead of breaking changes: Okapi prepares the fix before the change breaks your app. - Keep your workflow: every fix comes as a pull request your team reviews and merges. - Use it with any API, from the big names to the niche ones. How it works Okapi finds the APIs your code calls and tracks their changes. When a breaking change affects your code, Okapi's agents write the fix and open a pull request. The pull request says which API changed, what changed, when the change takes effect and which files it touches. Okapi never runs your code and never commits to your branches. Think of it as Dependabot for APIs. Who it's for - SaaS teams with a long integrations page. - Teams shipping AI agents that call many APIs. - E-commerce, logistics and fintech products built on third-party APIs. - Companies whose workflows run on many connectors (cybersecurity, healthcare, media and inbound marketing). - Agencies maintaining many client apps. - Researchers whose projects depend on many libraries and public APIs. Okapi is 100% free. Which API broke your app last? Tell us in the comments 💬

a PR that says which API changed, what changed and when it takes effect is way more useful than deprecation emails going to the inbox of someone who left the company lol

how do you catch a change that was never annouced anywhere??? some APIs just start returning a new field shape one morning with no changelog entry

Maker

 good question. Actually it is impossible to catch a change in an API that was never announced, even for us!

The good thing is that this usually do not happen on APIs that are used by many clients. However what happens on a regular basis is that vendors announce those changes very differently: an email, a blog post, a note on a changelog, a "deprecated" status on their spec, headers on their API response...

This is why it is so hard to keep up with all those services and their changes, and it's exactly where Okapi shines: Okapi agents track all of that stuff on a regular basis so builders can enjoy some peace of mind.

Including the API change's effective date in the pull request is useful. It gives the reviewer a concrete deadline alongside the code change, instead of another deprecation notice to track down.

Maker

 Indeed, Okapi does it. If you use it and have any feedback on the PR, the user experience or whatever, I'm all ears. Thanks for your comment :)