Quasa
Use QUASA App
Join the pioneer of Web3 crypto freelancing today!
Open
Finance & Markets

Keenable Raises $26M for a 100-Billion-Document Search Index

|Author: QUASA Editorial Team|5 min read| 3
Keenable Raises $26M for a 100-Billion-Document Search Index

On August 25, 2026, Keenable emerged from stealth with a $26 million seed round led by Accel. TechCrunch’s account of the launch names Conviction Partners and business angels as additional participants, says Keenable has 15 engineers across the United States and Europe and reports a plan to double headcount by the end of 2026.

Also on August 25, 2026, SiliconANGLE’s independent funding report described the same $26 million launch, additionally listed Brightwing Capital and scOp Venture Capital among the backers and said Keenable’s independent search index spans more than 100 billion documents. The product is intended to give AI agents programmatic access to web search and cleaned page content rather than provide another consumer-facing results page.

What the seed round is financing

Keenable expands the crawling, indexing and retrieval infrastructure financed by its $26 million seed round.

Keenable is taking on an infrastructure problem with substantial fixed and continuing costs. An independent web index requires crawlers to discover and revisit pages, processing systems to extract and normalize content, storage for documents and metadata, ranking systems to select results and serving capacity that can handle repeated API calls.

Those expenses do not stop once an initial index has been assembled. Pages change or disappear, duplicate copies accumulate and spam tactics adapt to ranking systems. Maintaining useful coverage therefore requires continuous recrawling, reprocessing and quality control, while every production query adds compute, network and support costs.

The hiring plan shows that the round is meant to support both technical expansion and a go-to-market operation. It does not, however, establish commercial scale: Keenable has not disclosed named customers, revenue, query volume, contract values or the share of announced production use that represents paid and recurring traffic.

How Keenable’s agent-oriented search works

A Keenable agent query returns ranked web pages and cleaned source content for a live task.

An agent can send a query to Keenable’s Search API, receive ranked web pages and use a companion function to fetch page content for a model. That workflow separates retrieval from the model itself: Keenable supplies source material, while the customer’s model or agent decides how to interpret it, combine it and act on it.

Keenable’s official product page claims an index of more than 100 billion documents, latency below 250 milliseconds at the 95th percentile in US East and production use at several unnamed AI labs and inference providers; it lists pay-as-you-go access at $4 per 1,000 requests, dedicated capacity at $1 per 1,000 requests for workloads of at least 100 requests per second and a Time Machine historical-search product available only through an early-access request.

The search-and-fetch design fits agents that need to gather evidence during a task instead of presenting links for a person to inspect. It also places Keenable in the same emerging infrastructure category as Microsoft’s agent search infrastructure, although the underlying indexes, product boundaries and access models differ.

Why 100 billion documents do not prove quality or low cost

Keenable serves pay-as-you-go searches and dedicated traffic of at least 100 requests per second under separate pricing tiers.

The index figure measures stated collection size, not relevance. It does not reveal how many documents are duplicates, obsolete pages or low-quality material, nor whether the ranking system consistently returns the best sources for a particular language, region or specialist subject.

Freshness is a separate property. A large collection can still lag behind current events if important sites are recrawled slowly or updated pages take too long to pass through processing and ranking. Keenable has not published an independent freshness audit showing recrawl intervals or measured ingestion delays across defined categories of sites.

The advertised request prices are similarly incomplete as a measure of workload economics. An agent may issue several searches, fetch multiple pages and retry queries before completing one user task. Its actual retrieval cost will depend on the number of calls, caching, traffic peaks, response sizes, failed requests and whether its volume is high enough to qualify for dedicated pricing.

Keenable displays its own NEEDLE comparison of result quality and public API prices, but a company-published benchmark is not an independent validation. The launch materials provide no third-party relevance test, serving-cost comparison based on a shared production workload or audit of the reported latency across regions and query types.

What the launch proves—and what remains private

Keenable has progressed beyond a concept: it presents a documented API workflow, public access tiers and an early-access path for historical search. Its founders have also secured a large seed round for the costly work of maintaining and serving an independent index.

The evidence is weaker on adoption and defensibility. The named publications repeat Keenable’s statement that several AI labs and inference providers use the service in production, but no customer is identified and no usage or retention data is available for outside review. Production use could range from limited workloads to a central retrieval dependency; the disclosure does not establish where current deployments fall on that spectrum.

The immediate result is a well-funded entrant with a visible commercial surface and an unusually large claimed corpus. Determining whether that scale produces better answers and sustainable margins will require evidence the launch did not provide: named deployments, independently measured relevance and freshness, and operating data that connects request prices with the full cost of serving high-frequency agent workloads.

Also read:

Share:

Subscribe to our newsletter

Get the latest Web3, AI, and crypto news delivered straight to your inbox.

0