Releasesby IbisOctober 2026
Update8 days agoUnverifiedAdded Oct 10, 2026
Pay per request with x402 , search and fetch can now be bought one call at a time, with no account and no API key. /v1/x402/search and /v1/x402/fetch answer 402 with an x402 offer; the client pays $0.01 in USDC on Base and retries, and gets the result with an on-chain receipt. Any standard x402 client works. See Pay per request .
Topics: AI agents, Pricing, Developer tools
More Keenable releases
Every Keenable releaseSeptember 2026
Keenable on Baseten , web search and page fetch run as server-side tools on Baseten Model APIs. Name the two tools in a chat request and the model searches and reads pages inside Baseten's inference loop; no MCP client and no Keenable key, because Baseten meters the calls onto your Baseten invoice.
August 2026
Point-in-time search , query_time is now documented on both the MCP tool and the Search API : search the index as it stood at an instant, and have relative date filters resolve against that instant rather than now. Two more search parameters , max_results caps how many results come back (1–50), and snippet_max_length caps the snippet per result.
July 2026
Prompt-driven extraction , the Fetch endpoint accepts a prompt , and returns what an LLM read out of the page for that instruction instead of the whole page. Usage and overrides over MCP , every authenticated tool call now reports its cost under _meta["keenable/usage"] , and an integrator can pin the search mode with _meta["keenable/overrides"] .
May 2026
Unauthenticated access , the CLI and MCP server now answer requests without an API key, on a shared public tier, so you can evaluate them before creating an account. See Authentication . Authentication & rate-limit guides , new Authentication and Rate limits pages cover the device-code login flow, API keys, and the unauthenticated vs. authenticated tiers.
June 2026
Live fetching on the Fetch API , the Fetch endpoint now accepts a live parameter to retrieve a page in real time instead of serving the cached copy. Use it when freshness matters more than latency.
April 2026
Keenable API launch , the initial public release of the Keenable platform for AI agents: the Search API ( /v1/search ), the Fetch API ( /v1/fetch ), the CLI , and the MCP server , one API key across all of them.
Also shipped on Oct 2, 2026
Keenable in October 2026PagerDuty Advance team-level permissions now Generally Available
Building on team-level permissions, Account Admins can now choose which AI agents are enabled for each team. This further empowers teams to roll out AI adoption with confidence. Learn more.
AI Gateway, Web Search API - Introducing Web Search API
Web Search API is now available in beta. Web Search API lets your AI agents and applications search the Internet and ground their responses in live information, instead of guessing URLs or relying on a model's training cutoff. At launch, you can choose between three search providers: Ceramic.ai, Exa, and Linkup .
KV - Workers KV namespace jurisdictions are now generally available
Jurisdictions for Workers KV namespaces are now generally available. When you create a namespace, you can set a jurisdiction to make sure the namespace's data is only durably stored within that region. Jurisdictions can help you comply with data localization regulations such as GDPR or FedRAMP. Supported jurisdictions are eu , us , and fedramp .
Repository security advisory comments API in public preview
You can now read, add, and edit comments on repository security advisories using the REST API, including advisories created from private vulnerability reports. Until now, the discussion on an advisory was only reachable in the web UI, even though it often holds the most useful triage context on a vulnerability report.
Note : Your clusters might not have these versions available
Note : Your clusters might not have these versions available. Rollouts are already in progress when we publish the release notes, and can take multiple days to complete across all Google Cloud zones. Version 1.36.4-gke.1495000 is now the default version for cluster creation in the Rapid channel.
You can use Vertical Pod Autoscaler (VPA) with Horizontal Pod Autoscaler (HPA) to automatically optimize...
You can use Vertical Pod Autoscaler (VPA) with Horizontal Pod Autoscaler (HPA) to automatically optimize container CPU requests for workloads that scale replicas based on CPU utilization. This feature is available in Public Preview on clusters running GKE version 1.36.3-gke.1630000 or later. For more information, see Rightsize HPA workloads with VPA .