// knotbind mend

When an API changes,your code is already fixed.

Mend watches the APIs your code calls. When a provider ships a change that breaks you, it finds the exact lines, fixes them, runs your own tests, and opens a draft pull request. You review and merge.

On every plan. Free connects 1 repo.

// two ways in

Try it in a minute, or connect your repo.

Try the demo

Enter your email on the demo page. A Slack webhook is optional.

Open the link we email you and press the Mend button. A made-up provider, Acme, removes a field.

You see the lines it broke, the fix, and a real draft pull request.

Open the demo

Connect your repo

On any plan, connect GitHub and pick a repo. Free includes one, Pro up to five, Business up to twenty.

Tick the APIs it calls: today the GitHub API and the OpenAI API.

When one of them changes in a way that breaks your code, you get a draft pull request with the fix.

Start free

// the loop

Five steps. You only do the last one.

1

Connect

Install the Knotbind Mend GitHub App on the repos you choose and pick the APIs each one calls.

2

Track

Mend reads each provider's public API description on a schedule and compares versions, field by field.

3

Detect

It finds the files and lines that use what changed, with a plain explanation and a severity.

4

Fix

It renames the code that used a removed field, runs your install, build and tests in a container, and opens a draft pull request.

5

Review

You read the diff, the explanation and the test result, then merge or close it.

// the other side

When an assistant tool breaks, Mend opens the pull request too.

Knotbind already checks the tools your AI assistants call. When one stops working, it drafts a repair and proves it in the Sandbox. Pick your MCP server repo once, and Mend opens a draft pull request there on its own, with a confidence score.

Be clear about what that pull request is: a repair note with the verified change, proven by a Sandbox re-run. It does not edit your server code yet and it does not run your tests, so you apply the change and run them before you merge.

// a draft pull request

What lands in your repo.

An example, with made-up names. Every pull request carries the severity, a confidence from 0 to 100%, the lines it touched and the result of your own tests.

Mend: fix 2 breaking changes from acme 2.0.0

Severity: high · Confidence: 85% · draft

Response field 'phone' was removed from GET /v1/customers/{id}. Used in 1 call and 5 field references across 3 files.

- const { phone } = customer;
+ const { phone_number: phone } = customer;

install passed · build passed · test passed

// safe to hand the keys to

It can only open drafts.

Never your default branch

Mend pushes branches named knotbind/mend/ and opens draft pull requests. It never merges and never writes to your default branch.

Least access

A GitHub App with short-lived access to only the repos you pick. Uninstall it any time.

Tests decide, then it asks

If your tests fail or Mend is not sure, you get an issue that explains why and offers the pull request.

Easy to close, easy to undo

Close a pull request and Mend will not reopen it. The fix is one commit, so reverting it is one command.

Every step is logged

Each detection, patch, test run, pull request and issue is written to your Audit Record.

Your code stays yours

No file names or code go to an AI model. Severity and fixes come from rules you can read in the pull request.

// plans

On every plan.

1 repo on Free, up to 5 on Pro and up to 20 on Business. Enterprise agrees a repo limit in writing.

Knotbind Mend is included in Free, Pro ($199 per month), Business ($399 per month) and Enterprise.

See the plans

// questions

Mend questions.

What is Knotbind Mend?

A service, on every plan, that keeps your own code in step with the APIs it calls. It watches the public API descriptions of the providers you pick. When a change would break code in a connected repo, it finds the affected lines and opens a draft pull request with the fix.

Does Mend also handle breaks in the tools my AI assistants call?

Yes. When a Check shows that a tool an assistant such as Claude or ChatGPT calls has stopped working, Knotbind diagnoses it, drafts a repair and proves it in the Sandbox. If you have marked your MCP server repo, Mend then opens a draft pull request there on its own, with a confidence score. The pull request carries a repair note with the verified change. It does not edit your server code yet, and it does not run your tests, so apply the change and run them before you merge.

Which providers and repos does it support?

Today the GitHub REST API and the OpenAI API, on TypeScript or Node repos hosted on GitHub. Other languages and other Git hosts are not supported yet. Mend reads types in your code, so a response that is not typed is reported but not edited.

Can it change my default branch?

No. Mend only pushes branches named knotbind/mend/ and opens draft pull requests. It never writes to your default branch and never merges anything. You review, test and merge.

What if the tests fail or Mend is unsure?

Then it opens an issue instead, explains why, and offers the pull request. Comment /mend open-pr on the issue, or use the button in the dashboard, and Mend opens it as a draft with the reason on it.

Does Mend run my code?

It runs your repo's own install, build and test scripts on the patched code in a throwaway container. Install has network access with dependency scripts turned off. Build and tests run with no network and no secrets from Knotbind.

What does it send to an AI model?

Only the provider's side of a change, such as the operation and the field that was removed. Your file names, paths and code are not sent. Severity and the fix itself are decided by rules, not by a model.

How do I opt out?

Pause or remove a repo, or dismiss a single change, in the dashboard. A repo can also carry its own opt-out in a .knotbind.yml file. Closing a pull request dismisses its changes, and Mend does not reopen them.

What does it cost?

Mend is on every plan. Free connects 1 repo, Pro up to 5 and Business up to 20. Enterprise agrees a repo limit in writing. You name each repo, and the names appear in your dashboard sidebar so you can switch between them.

// contact

Tell us what your customers should be able to ask.

Send a message. We reply with what to connect, which assistants to target, and a fixed price. No call.

Contact us