What Knotbind limits, and what it does not claim.
The numbers that apply to every plan, and the things a passing Check or a successful call does not prove. Feature pages stay short because this is collected here.
Plan limits
| Free | Pro | Business | |
|---|---|---|---|
| Price | $0 | $199 per month | $399 per month |
| Active Checks, across all servers | 3 | 10 | 25 |
| Checks run | Daily | Hourly | Every 5 minutes |
| History | 7 days | 90 days | 365 days |
| Members | 1 | 5 | 20 |
| Mend: GitHub repos, your own APIs | 1, 1 | 5, 3 | 20, 10 |
Knotbind suggests one contract Check for each tool, but only approved Checks count against the limit. See MCP servers.
API limits
Request rates, body size and retry rules are on the Agent API page. Credential vault limits are on Credential vault.
What Knotbind does not claim
| When you see | It does not prove |
|---|---|
| A passing contract Check | That Claude, ChatGPT or Cursor has connected. Real client proof is recorded separately or detected through the relay. |
| An approved repair | That your API or repository changed. Approval changes Knotbind's Check. See Reliability. |
| A successful tool call | That an order was placed or a payment was made. Read the run's evidence. |
| A Mend pull request | That the fix is right. Mend states a confidence and your tests' result; you review and merge. |
| An Apify run that succeeded | That an MCP tool, schema or agent workflow still works. |
| A demo run | Anything about your production system. |