# Kenso status

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

Whether each part of Kenso is working right now. This page checks every minute from a server outside the API's own, so it still answers when the API does not.

**Status unknown right now.** Checked 2026-11-16 01:04 UTC. The page refreshes every minute.

## Components

- **API: Operational.** `api.ken.so` answers requests.
- **Sending: Unknown.** The email send dispatcher is running. It runs every 15 seconds.
- **MCP: Operational.** The MCP server at `mcp.ken.so` answers its health check. Last activity 2026-11-16 01:04 UTC.
- **Webhooks: Unknown.** The webhook dispatcher is running and handing events to delivery. It runs every minute. One endpoint that fails does not count.

## For scripts and agents

`GET https://api.ken.so/v1/status` returns the API, sending and webhook statuses as JSON, with no API key. This page is also Markdown at [/status.md](/status.md).

## Something wrong that this page does not show?

Email [contact@ken.so](mailto:contact@ken.so) with the `requestId` of the failing response. Changes to the API are in the [changelog](/docs/changelog).
