API Change Agent · pilot stage

When your API changes, your users’ code gets a pull request.

A renamed method, a moved package, a new client: every breaking release leaves your users to update their code, and many don’t. The API Change Agent finds every affected call in a user’s project, fixes what can be fixed exactly, and opens a pull request that says what changed, what still needs a person, and whether the project’s own tests still pass.

Ask about a pilot The company

How it works

Read the changeFrom your migration guide, or by comparing your old and new OpenAPI specs, into a list of changes you approve.
Fix what is exactRenames are applied by fixed rules, never guessed. Everything else is flagged with what to do.
Test the restOptionally, AI proposes fixes for the flagged items. They are kept only if the project’s tests pass.
Open the pull requestAs a GitHub Action in the user’s own repository. Their code never leaves their GitHub, and nothing is merged automatically.

public projects checked: 50
unseen projects fully handled: 15 of 20
automatic fixes right: 63 of 64
of AI per typical file: $0.01–0.06

Measured in September 2026 on public open-source projects still on the old OpenAI SDKs (Python 0.x, Node v3), with every fix checked by Pyright or TypeScript against the new SDK. “Unseen”: 20 projects the rules had not been tuned on. “Fully handled”: every break fixed or flagged for a person. Automatic fixes counted in the projects’ own code. AI cost measured with Claude Opus 5, and only when AI is used.

What it is

A command-line tool and a GitHub Action. Change lists you review before they are used. A test gate: AI edits go into the pull request only when the tests pass. Your choice of AI model, a cost estimate before every run and a hard spending cap.

What it is not

Finished: it is at pilot stage, with no paying customer yet. Every language: JavaScript, TypeScript and Python today. Unsupervised: in about one project in four it missed something or got something wrong, which is why every change goes through review and the project’s own tests.

Who it is for

API and SDK teams shipping a breaking release, or moving to a different SDK generator, who would rather hand their users a reviewed pull request than a migration guide and a deprecation date.

One rule it shares with GovernanceHub

Rtavan does not sell the API Change Agent to any company GovernanceHub lists or assesses — 22 today, read from the registry as this page loads. If a customer is ever added to the registry, the relationship is recorded on its assessment and the independence claim is withdrawn, automatically: the same rule as everywhere else on the registry.

A pilot

Send your last migration guide, or your old and new OpenAPI specs. Within a week you will see exactly what the agent would change in public projects that use your SDK, with the pull request it would open. Nothing is sent to your users.

Ask about a pilot →