One API across Meilisearch, Typesense, and Elasticsearch. Pick your engine per index. Bring your own infra. MCP, RAG, and chat included.
For BYOE indexes, your documents stay in your engine. We don't lock you into one backend or force one engine on your whole company.
# Storefront catalog → Meilisearch (typo-tolerant, fast)
curl -X POST https://headband.dev/v1/indexes \
-H "Authorization: Bearer hb_adm_..." \
-d '{ "uid": "products", "engine": "meilisearch" }'
# Logs → Elasticsearch (aggregations, scale)
curl -X POST https://headband.dev/v1/indexes \
-H "Authorization: Bearer hb_adm_..." \
-d '{ "uid": "events", "engine": "elasticsearch" }'
# Same API key. Same SDK. Different engines.curl -X POST https://headband.dev/v1/search \
-H "Authorization: Bearer hb_src_..." \
-H "Content-Type: application/json" \
-d '{ "index": "products", "q": "macbook" }'
// Response in ~2ms — engine routed automatically
{
"hits": [
{ "id": 1, "title": "MacBook Pro", "price": 1999 }
],
"engine": "meilisearch",
"processingTimeMs": 2
}Build search UIs in minutes with @headband/react. Hooks, components, and InstantSearch-compatible API.
import { headband, HeadbandProvider, SearchBox, Hits, RefinementList } from '@headband/react'
const client = headband('https://headband.dev', 'hb_src_your_key')
function App() {
return (
<HeadbandProvider client={client} index="movies">
<SearchBox placeholder="Search movies..." />
<RefinementList attribute="genres" />
<Hits />
</HeadbandProvider>
)
}Catalog on Meilisearch, logs on Elasticsearch, autocomplete on Typesense — all under one account. Nobody else lets you mix.
Bring Your Own Engine. Point any index at your own cluster. Compliance, residency, and self-hosting handled by you.
llms.txt, RAG-ready endpoints, and an MCP server. Headband is the retrieval substrate for your agents.
Meilisearch, Typesense, Elasticsearch. Same SDK, same dashboard, same filter syntax. Swap engines without touching client code.
Admin keys for writes, search keys for reads. Project-scoped, prefix-enforced, tenant-isolated by default.
Top queries, zero-result rates, response times. Per-engine, per-index, in the dashboard. No extra service to wire up.
llms.txt and RAG-ready endpoints ship today. MCP server and /v1/chat are live. Same API, any engine, any agent.
Auto-generate a standards-compliant llms.txt so AI crawlers know what your indexes contain.
Clean text chunks, no HTML, structured metadata. One call feeds your RAG pipeline.
Engine-agnostic MCP server and a chat completions endpoint grounded in your indexes. Live now.
See the engines compete in real time
Try the ShootoutFree to start. Scale when you need to. Self-host is always free.
For side projects and experiments.
For teams shipping real products.
For organizations with serious retrieval needs.
All plans include all 3 engines. Self-hosting is always free. See full pricing details
Free to start. No credit card required.
Create your account