Skip to main content
Email support@keenable.ai for anything about your account, billing or the API. Ask other questions and talk to the Keenable team in the Keenable Discord. You can also use the contact form.

Ask in Discord

The Keenable Discord is the place to ask how to use search, fetch, Monitors, the SDKs, the CLI or an integration, and to talk to the Keenable team. Never post an API key there. For a problem with your account or billing, email support@keenable.ai instead.

Check service status

The status page at status.keenable.ai shows whether the Keenable Search API and Content API are up, with 90 days of uptime history. Check it first when requests fail with 5xx errors or time out. Fetch runs on the Content API.

Report a bug in the SDKs or the CLI

Open a GitHub issue in the matching repository:

What to include

  • The X-Request-Id header value from the response. Search and fetch responses carry it, and Keenable uses it to find your request in the logs. Error responses carry it too, and repeat it as request_id in the body. If you have no response at all, for example after a timeout, include the time of the request instead.
  • Your SDK or CLI and its version, for example keenable 0.1.3 for Python.
  • The request, without your API key: the endpoint, the parameters, and the status and body you got back.
Before you write, check Errors and the FAQ. Most statuses have a fix you can apply right away. To look up a field or term, see the Glossary.

Report a problem from an agent

If your agent is connected to the Keenable docs MCP server, it can report a problem with the submit_feedback tool. Ask it to include the page, what it expected, what happened, and the X-Request-Id value if it has one.