Keenable AI (@KeenableAI) header
Keenable AI (@KeenableAI) profile picture

Building web search infrastructure for AI labs and agents

San Francisco, California
Joined February 2026
Photo by Keenable AI (@KeenableAI)Photo by Keenable AI (@KeenableAI)Photo by Keenable AI (@KeenableAI)Photo by Keenable AI (@KeenableAI)Photo by Keenable AI (@KeenableAI)
Keenable AI retweeted
Each agent will need its own search API key to get personalized results. Excited to work with @agentmail on this. Two agents search “Andrey Styskin biography”. HR wants artifacts: projects I’ve built, articles I’ve written. Sales wants common ground: past companies, communities, shared connections. With separate IDs, @KeenableAI will learn from the results each agent looks and personalize retrieval and ranking. We’re building the whole search stack to connect each agent with the knowledge it actually needs.
Keenable 🤝 AgentID @KeenableAI is web search infra for AI labs and agents. Now your agent can Sign in with AgentID and get its own account, API key, and usage. Add AgentID to your app with one prompt. Read on learn more.
5
18
1,183
Keenable AI retweeted
Introducing Keenable Dynamic Snippets Now your agent can spend 50% fewer tokens on search tasks and look deeper into documents. Enabled for everyone. Read our technical report to see how we built Dynamic Snippets while preserving our 200ms p95 search latency: keenable.ai/blog/keenable-sn…
3
7
2
34
1,845
Keenable AI retweeted
We keep building the fastest way to find information in Internet. Now 2x more token efficient for your agents. Read our tech report how we built it and what the impact is on agentic benchmarks.
Introducing Keenable Dynamic Snippets Now your agent can spend 50% fewer tokens on search tasks and look deeper into documents. Enabled for everyone. Read our technical report to see how we built Dynamic Snippets while preserving our 200ms p95 search latency: keenable.ai/blog/keenable-sn…
4
28
785
Keenable AI Open-Sources NEEDLE: A Live Search Benchmark That Rebuilds Its Query Set Every Hour Most search benchmarks are a fixed question set with a public answer key. That's not a benchmark for agents — because an agent with a fetch tool can just download the key mid-evaluation. Keenable open-sourced NEEDLE — a live search benchmark that rebuilds its query set instead of freezing one. News queries regenerate every hour from RSS feeds and Google Trends. Finance, scholar, and legal gold regenerates daily from public registries, SEC XBRL, arXiv, Europe PMC, CourtListener, and the eCFR. Rare-entity queries are sampled daily from public agent-trajectory logs. Here's what's actually interesting: → Queries are archived publicly after every run, so the defense isn't secrecy — it's that each run scores engines on queries newer than the models being tested → 18 engine configurations from 14 providers, one protocol: same query text, same 2,000-character evidence cap, one call at a time, judge blind to engine identity → Every score is read against ultimate, a pooled oracle engine that separates "this engine ranked badly" from "nobody found better." On rare-entity queries from real agent logs, the leader sits at 0.533 of that ceiling → There's an index-independence audit. Agreeing on good results proves nothing, so it flags a pair when they share a below-relevance URL, or share three-plus URLs on one query. In the published overlap data, Brave and You dot com are flagged on 89% of comparable queries Latency is treated as a quality metric — agents call search dozens of times per task, so p50 to p95 lands inside the user's wait. Full analysis: marktechpost.com/2026/08/31/… Technical Details: keenableai.github.io/needle/ @KeenableAI
2
6
28
138,138
Time per task includes both measured search time and model time. The one-shot model-only baseline takes ~13.8s per task with zero search time and scores 33 on the Artificial Analysis Search Index. All search API provider runs see an increase on baseline model-only time, ranging from +1.3s (Keenable Search (realtime)) per task to +41.3s per task (Firecrawl Search)
2
3
1
36
10,308
Keenable AI retweeted
Your voice agent should know how many E's the number 17 has. And it should also be able to search the web instantly for you. You can now integrate the @KeenableAI web search API with Gradium's API to build low-latency, voice-enabled web search. Check out our latest demo.
3
6
2
29
4,475
Keenable AI retweeted
didn’t think this would happen for a while, but now I consistently downgrade model for chat queries I know are not that hard, should be mostly retrieval/ai search api bc I want faster speed cc: @KeenableAI
16
2
1
81
14,705