Know which agent link broke and where.

Configure actionable alerts, recurring readiness checks, OpenAPI drift monitoring and Owner-approved plan requests.

Set up customer alerts

Open Settings in the customer dashboard. Configure email, a Slack incoming webhook, and/or a signed HTTPS webhook. Alert content names affected assistants, the failing layer and endpoint/tool, available evidence, and concrete recheck steps.

Monitor readiness and API changes

Readiness checks run weekly on Free, daily on Pro and every six hours on Business. A score drop above the configured threshold or a failing regression sends an alert. OpenAPI drift uses the stored normalized description as a baseline. Breaking changes alert once per fingerprint; the Owner explicitly accepts a new baseline after updating the integration.

MCP tool drift and server health

Each MCP server in your registry is polled on its own schedule, and every tool schema is fingerprinted. A change that breaks callers — a tool removed, a required parameter added, a parameter type changed — opens a Finding and sends an alert naming the tool and what changed. A change that does not break callers, such as an added optional parameter, is recorded without an alert.

Each server also carries its own status. A server that fails a poll is degraded; one that fails three polls in a row is offline and alerts the Owner once. When it answers again the alert is cleared, so a later outage is reported once more rather than being swallowed.

See MCP servers for the whole model.

Verify webhook signatures

Generic webhook requests carry X-Knotbind-Signature: t=<unix>,v1=<hex>, the event and delivery IDs. The hex is HMAC-SHA256 over the exact raw request body prefixed with t.. Reject stale timestamps (over five minutes), parse the raw body only after signature verification, and compare MACs in constant time. The secret is shown once when created or rotated.

Plan approval

An agent can use POST /api/v1/billing/plan-request or the MCP tool request_plan_change. The Owner gets the request on Billing and can approve to open Stripe Checkout or decline. This does not automatically charge or change a plan.

One-time customer API actions

Use POST /api/v1/tools/call or MCP tool call_tool_once to call a connected customer's MCP tool exactly once and get its result. Write-capable tools require explicit allow_write: true consent; this call does not become a scheduled Check. Knotbind's Stripe Checkout is only for a Knotbind subscription. Customer orders and payment links must be created by the customer's own API/MCP tool.

See the Agent API and implementation/security details in docs/alerts.md.