Reference

Every reference page, grouped by what you are trying to do. If you are new here, start with Lists — a list holds your records, and everything else in Search Stack hangs off one. Prefer to search: the box in the sidebar covers every page below, section by section.

Start here

• Lists — what a list is, and the path from creating one to searching it.
• Fields — searchable, facet, coordinates and resource fields, and what each lets search do.
• Searching — matching on words and on meaning, scores, and how results are ordered.
• Groups — search several lists as one, with merged results.

Keeping data in sync

• Feeds — what a feed is: a source polled on a cadence, staged as a file, imported into a list.
• Website Feed — point it at a section of your site and every page under it becomes searchable.
• RSS Feed — follow a feed and index each new item as it is published.
• API Feed — pull records from your own endpoint on a schedule.
• Notion Feed — make a Notion workspace searchable.
• Your Files Feed — drop files in a store and have them imported and re-imported automatically.
• Media Stores — where your files live, the file editor, and sync badges.
• Cleaning — tidy incoming records before they are indexed.
• Gates — rules that check, rewrite, hold back or refuse a record on the way in.

Search features

• Suggestions — as-you-type typeahead from your own data.
• User Generated Suggestions — suggestions that improve as people search.
• Image Search — search by a picture instead of words.
• Playground — try queries against a list and see what ranking does.
• Components — the front-end autocomplete library: install, options, events, styling.

Measuring quality

• Evaluations — turn “is my search any good?” into a number you can watch for regressions.
• Judges — have a model score results against your own instructions.
• Rerankers — bring your own reranker and attach it to a group.
• Embedding Models — bring your own embedding model; changes apply in the background.

Running it in production

• Search Servers — shared versus owned capacity, regions, and transfers.
• Caches — reuse recent answers; use the built-in cache or your own Redis.
• API Versioning — what bumps a version, pinning, migrating and restoring.
• Telemetry Destinations — export traces, metrics and logs to your own stack.
• Webhooks — get told when something happens, signed and retried.

Accounts and access

• API Keys — create a key, choose its permissions, rotate it.
• Credentials — store provider keys once and reuse them, encrypted at rest.
• Contributors — give teammates access, and what each permission allows.