Next.js + React
LiveUse @headband/react in App Router or Pages Router search surfaces.
npm i @headband/reactHeadband gives developers one retrieval API, then meets them where they are: React, server-rendered apps, relational databases, commerce systems, webhooks, and A/B/C search experiments.
Adoption path
Live means a first-party package or endpoint exists today. Recipe means the pattern is documented and uses stable REST/SDK primitives.
Use @headband/react in App Router or Pages Router search surfaces.
npm i @headband/reactCall the REST API from loaders/actions and hydrate client-side refinements.
npm i @headband/reactRender static catalog shells and hydrate Headband search islands only where needed.
npm i @headband/reactUse fetch against /v1/search from load functions or progressive-enhanced forms.
npm i @headband/clientIndex relational records with sync scripts, then render server-owned search pages.
curl https://headband.dev/api/v1/searchRun a scheduled SQL export into /v1/bulk, then validate with /v1/search.
Sync model
script
Env: DATABASE_URL, HEADBAND_URL, HEADBAND_ADMIN_KEY
Map table rows into documents and batch them through the Headband bulk API.
Sync model
script
Env: MYSQL_URL, HEADBAND_URL, HEADBAND_ADMIN_KEY
Use product webhooks or scheduled exports to keep catalog search fresh.
Sync model
webhook
Env: SHOPIFY_ADMIN_TOKEN, HEADBAND_ADMIN_KEY
Mirror products/prices into an index for account portals, docs, and internal tools.
Sync model
webhook
Env: STRIPE_SECRET_KEY, HEADBAND_ADMIN_KEY
Managed scheduling, retries, logs, and secret storage belong in the connector runtime roadmap.
Sync model
managed-roadmap
Use Headband indexes as experiment variants, split traffic in your app, and write analytics events with the variant name. Your app owns traffic allocation; Headband supplies stable search endpoints, and your product analytics remains the source of truth for conversion.
Split traffic across Meilisearch, Typesense, and Elasticsearch indexes for the same corpus.
Metrics: conversion, zero_result_rate, p95_latency_ms
Compare synonyms, typo tolerance, filters, and boosts without changing client code.
Metrics: click_through_rate, add_to_cart_rate, search_exit_rate
Compare lexical, vector, and hybrid retrieval before rolling a RAG flow to everyone.
Metrics: answer_acceptance, grounding_failure, latency_ms