Category
Search as a service
One question, 15 recorded answers across 2 tools. Each run used a separate session. The table counts vendor mentions. 2 of 6 vendors we measure in this category were never named once.
These are dated samples from different tools and setups, not a controlled comparison of model quality.
Measured access checks
We measured 6 of the 6 providers in this category. None cleared every barrier we test. These HTTP checks do not establish integration success. Feature fit, price and support are outside their scope.
Clear (0)
Nobody cleared every measured barrier.
Blocked (5)
- meilisearch.com - no door built for a machinemeasured 2026-08-24 · evidence
- typesense.org - no door built for a machinemeasured 2026-08-24 · evidence
- elastic.co - the signup form is not in the served HTMLmeasured 2026-08-24 · evidence
- oramasearch.com - no door built for a machinemeasured 2026-08-24 · evidence
- searchkit.co - no door built for a machinemeasured 2026-08-24 · evidence
Unknown (1)
- algolia.com - no measured barriermeasured 2026-08-24 · evidence
The question we asked
Our users cannot find anything in our knowledge base because the search is a SQL LIKE query. I want typo tolerant search with filters over our own documents, ranked sensibly, without hiring a search engineer. Node backend, a few hundred thousand documents. Which service would you use, and what else did you consider?
codex codex-cli 0.147.0 (default), 5 runs, 2026-08-17. The question asks for a recommendation without naming a vendor.
The Claude Code runs could read the operator instructions (CLAUDE.md). Those instructions request Polish, so some answers are in Polish. Results describe this setup, not an agent at your customer.
Named, and measured
| Vendor | Named (Codex)default · 2026-08-17 | Named (Codex)default · 2026-09-02 | Named (Claude Code)sonnet · 2026-08-16 | Named first (Codex) | Scan |
|---|---|---|---|---|---|
| algolia.com | 5/5 | 5/5 | 5/5 | 5 | 10/15 |
| elastic.co | 5/5 | 5/5 | 5/5 | 0 | 9/15 |
| meilisearch.com | 5/5 | 5/5 | 5/5 | 0 | 9/16 |
| typesense.org | 5/5 | 5/5 | 5/5 | 0 | 10/17 |
| oramasearch.com | 0/5 | 0/5 | 0/5 | 0 | 7/12 |
| searchkit.co | 0/5 | 0/5 | 0/5 | 0 | 5/10 |
Named counts runs that mentioned a vendor. Named first counts runs that mentioned it before any other vendor we measure. Mention order does not establish a purchasing decision.
A batch of 5 runs is a small sample. A one- or two-run difference does not establish a ranking. Read what the agent actually answered or how every number here is measured
Building an agent or comparing providers programmatically? Download this category as JSON with dated measurements and the recorded access barriers.