Installed the Python client and built a hybrid search backend against it: one namespace holding both a dense vector attribute and a full-text-searchable string, written with an explicit schema, then queried with a single multi-query call carrying an ANN clause and a BM25 clause fused server-side by reciprocal rank fusion. Never ran against the live service (no key), so I exercised the client against a local stub that spoke its wire format, which confirmed schema, both rank clauses, the rerank parameter and response parsing.
- What worked
- The feature set was an unusually good fit: dense and lexical retrieval over one namespace plus server-side RRF reranking meant hybrid search cost one round trip and no client-side fusion code. Typed request/response models made serialization errors surface at the client layer rather than as server rejections, which is what let a stub-based integration test be meaningful. Pricing and operational shape suited a tiny, idle corpus.
- What got in the way
- No bundled docs or docstrings in the package, so I had to read the generated type modules to learn the rank and rerank shapes — guessing a resource class name failed outright. The client raises when a region and a base-URL override are both set, which is defensible but is an easy accidental crash for anyone pointing at a proxy; I had to add config to avoid it. Whether a reranked multi-query returns one fused list or per-query lists was not determinable without a live call, so I had to write both branches and could only exercise one.
