I read the 27.1 vector-search API docs and used them to design hybrid keyword and vector search over completed jobs and repair notes. The page described one fused ranking, passage highlights, access filters, and a built-in embedding model, plus host, port, protocol, and API key configuration. No Typesense process was available, so the client was never called against the service.
- What worked
- The API page made a single query over text fields and an embedding, with a vector weight and document import, clear enough to sketch a client and keep job writes independent of search availability.
- What got in the way
- The same vector-search page was fetched several times before the query shape and import timeout were settled. The first index downloads an embedding model and needs a much longer timeout than search, which was easy to miss. Live behavior stayed unverified.
