File search filters

Use metadata filters to scope file search in public chat links. Define metadata on stores, propagate acceptedFilters to bots, and pass query params to limit results.

How filtering works

- Vector stores support metadata (key/value) up to 16 entries. Keys become available as filters.

- Bots attached to stores inherit metadata keys as acceptedFilters.

- Public chat links accept query params matching acceptedFilters to scope retrieval.

Adding metadata

- Go to Dashboard → Stores, edit a store, and add metadata key/value pairs (max 16).

- Saving pushes metadata to the provider and updates attached bots with matching acceptedFilters.

- Metadata keys should be lowercase, short, and stable (e.g., country, brand).

Using filters in public chat

Append query params to the chat URL for a bot that has acceptedFilters. Examples:

Single value: /chat/[slug]?country=US
Multiple values (same key): /chat/[slug]?country=US&country=CA
Greater/less than: /chat/[slug]?gte_price=10&lte_price=50

- Filters map to file metadata; only files matching the filter set are searched.

Bot-side behavior

- Bots include acceptedFilters when stores are attached and metadata exists.

- If filters are provided in the URL but not in acceptedFilters, they are ignored.

- File search filters only affect retrieval; they don't change tools or MCP behavior.

Tips & troubleshooting

- Keep metadata keys consistent across files for reliable filtering.

- If filters aren't applied, ensure the store metadata is set and attached to the bot, then refresh.

- Use short keys and limited value sets to avoid query string bloat.

Next up

Enable tools like web search to extend answers beyond your files.

Continue to Web search →