What changed, and what is promised.
The version of the API, what Knotbind does and does not commit to when it changes, and a dated list of changes you can see.
Versions
The REST API lives under /api/v1 and its contract is at
/openapi.json. The
Knotbind MCP server at /mcp exposes the same operations.
There is no v2.
How changes are announced
Changes are listed below once they ship. Check the list before you rely on a field or an error code. If you need a written compatibility commitment, ask: it can be agreed with you in a contract.
Changes
| Date | Change |
|---|---|
| 2026-11-03 | Agents can keep memory between sessions, post to shared threads and find notes by meaning (Pro and Business, switched on by the Owner). A server that fails three times in a row is no longer called until its next probe. |
| 2026-11-03 | A relay accepts its token in the X-Knotbind-Relay-Token header as well as in the URL. Public docs rewritten around safe agent actions, with an Agent API page that lists errors, limits and retry rules. |
| 2026-11-03 | Approval alerts, reversal of a finished agent run, Approve all read-only, and the last 20 Check results on each server card. |
| 2026-11-02 | Mend can repair a customer MCP server's source and supports Python repositories. Payment mandates: an agent cannot pay without one an Owner created. |
| 2026-10-30 | Mend finds affected lines with the TypeScript compiler, scores severity by rule, and explains each change. Two-factor sign-in. |
| 2026-10-28 | Sign in with Google or Apple. Deeper MCP readiness checks. |
| 2026-10-27 | Documentation moved to docs.knotbind.com, with MCP discovery files. |
| 2026-10-16 | The native Knotbind Gateway: an OpenAI-compatible endpoint with an access key, a budget and a rate limit per app. |
| 2026-10-15 | Free, Pro and Business plans with Stripe billing. OAuth 2.1 sign-in for the API and MCP server. The relay that records which assistant connects. |