https://api.keenable.ai and the tools of the MCP server at https://api.keenable.ai/mcp. Agents and SELECT are separate services at their own URLs. They are not covered yet; changes to them are announced in the changelog.
Versioning
The API version is part of the path. Search and Fetch live under/v1: /v1/search, /v1/fetch, and their /public and /x402 twins.
Within a version, Keenable makes only backward-compatible changes. They can ship at any time and are announced in the changelog:
- new endpoints;
- new optional request parameters;
- new fields in responses;
- new values for a field that names a mode, status or type;
- changes to ranking, snippets and index coverage that change which results come back.
- removing or renaming an endpoint, a request parameter or a response field;
- changing the type of a field, or what a value means;
- making an optional parameter required, or rejecting input that used to be accepted;
- changing a parameter’s default.
/v2, or through the deprecation policy below.
The same rules cover the tools of the MCP server (search_web_pages and fetch_page_content): their names, their arguments and what those arguments mean.
Deprecation policy
When an endpoint, a parameter, a response field or an MCP tool is deprecated:- it is announced in the changelog and by email to organization owners, with what replaces it and the date it stops working;
- it keeps working for at least 90 days after the announcement;
- it is marked deprecated in this reference for as long as it still works.
- Security and legal. If keeping something running would put customers or third parties at risk, or would break the law, it can change sooner. Notice goes out as soon as it can.
- Experimental features. Anything the docs mark as experimental, beta or early access can change or be removed without the notice period.