Okapi

Okapi is a free GitHub App that watches the third-party APIs your app and AI agents call and opens a pull request with the fix before a breaking change hits. It is built for developers whose applications and agents depend on external APIs, where a single changed field, renamed parameter, or retired endpoint can take a production app down. Okapi describes itself as Dependabot for APIs: instead of waiting for a deprecation email or manually reading changelogs, you connect a GitHub repository and Okapi keeps your code up to date with every API it calls. The goal is simple — your app keeps working and your team stops chasing changelogs. APIs change all the time, and keeping up with every API's changelog is a hassle. Deprecation emails get lost, nobody has time set aside for the work, and no one owns it. Still, a small field change in an API response can take your whole app down — as Okapi puts it, a tiny update can bring down a big app. The problem is not that providers fail to announce changes; it is that the announcements arrive in many different places and formats, and the people responsible for a repository are busy building. Okapi exists to close that gap by watching for changes continuously so developers can focus on building rather than on maintaining connectors and reading release notes. Getting started takes one click. You connect your GitHub repository through the Okapi GitHub App, and Okapi then finds the APIs your app depends on by reading your code. It looks for the API calls the repository makes, from the big names to the niche ones that break more often, and keeps track of their changes. Installation is described as "1 click, then forget it," and the product is 100% free. Because discovery is based on the code you already have, there is no configuration list to maintain by hand and no inventory of providers to assemble: Okapi finds them in your repo for you and begins watching them. Okapi monitors each API call individually and suggests a fix before it breaks. Today it reads 1,173 API providers' own pages and tracks 841 upcoming breaking changes, according to the website. That coverage matters because deprecations and breaking changes are usually published by each provider on its own pages, in its own format, on its own schedule. By reading those pages directly, Okapi can surface an upcoming change — such as a field that will handle null values differently from a given date — and connect it back to the specific places in your code that use the affected call. The result is a continuous watch over the APIs your app depends on rather than a one-time audit. When an API call is deprecated or about to break, Okapi opens a pull request with the fix before it fails. The pull request is not a generic warning: it contains the actual change your code needs. In the Stripe example shown on the site, okapi[bot] opens a pull request titled "Update Stripe API for upcoming customer.address change", wants to merge one commit from a branch named okapi/stripe-customer-address into main, and explains in a comment that Stripe is changing how customer.address handles null values on October 15. The comment lists the effective date, the API, and the number of affected files (two), and the diff updates both files to handle the new response format. The pull request also carries release notes and a "what changed" section plus api-changes and stripe labels, so a reviewer can understand the change without hunting for context. Okapi works with any API, not only a fixed set of well-known providers. The site's examples span many languages and services: an OpenAI call updated from max_tokens to max_completion_tokens; a PubMed query changed from sort "date" to "pub_date"; a verification request that gains a verify_profile_id field; a notification URL moved to a new push endpoint; an ip-api lookup switched from HTTPS to HTTP; a Figshare download moved to the v2 API; a Mojang profile path corrected; and a Gemini configuration changed from a thinking budget to a thinking level. Each diff is small — often one or two lines — which is exactly the point: the changes that break production are frequently tiny, and they are easy to miss when nobody is watching every provider's changelog. Okapi's approach mirrors dependency automation, which is why it calls itself Dependabot for APIs. Rather than pushing commits directly, it opens a pull request for every change so a human reviews and merges it. The site states that Okapi never commits to your branches: every change comes as a pull request you review. If you do not merge the pull request, nothing changes in your code; the pull request stays open until you merge or close it. That design keeps developers in control while still removing the detective work of finding the change and the mechanical work of applying it. The stated benefits are straightforward: no more time spent maintaining connectors, and improved reliability over time. Instead of learning about a breaking change from a production incident, teams see a pull request with a fix and an explanation before the effective date. Deprecation emails that get lost no longer matter as much, because the watch is continuous and attached to the code that makes the call. Because the fix arrives as a reviewable pull request, teams can adopt it on their own schedule, inspect the reasoning, and keep their normal code review process intact. Concrete scenarios follow directly from the site's examples. A billing service that reads customer.address from Stripe can receive a pull request ahead of the October 15 null-handling change. An application calling OpenAI can be moved from max_tokens to max_completion_tokens. A literature search tool using PubMed can have its sort parameter corrected. A service calling a geolocation or media API can have a changed URL or protocol updated. Teams running AI agents that call external services can keep those agents working as providers evolve. And teams depending on niche APIs that break more often get the same monitoring as those using the largest providers. Okapi is aimed at developers whose apps and AI agents depend on third-party APIs, and at teams that do not have anyone specifically assigned to tracking provider changelogs. The access required is limited: Okapi reads your code to find the API calls it should watch, and it never commits to your branches. Removal is equally simple — uninstall the Okapi app from your GitHub settings and it stops right away. The product is 100% free, installs in one click, and works with any API, so there is no pricing tier or provider list to evaluate before trying it. In short, Okapi brings dependency-style automation to the APIs your code calls. It discovers the APIs in your repository, watches their providers for deprecations and breaking changes, and opens a pull request with the fix before the change can break your app — free, with one-click install, and with every change left for you to review.