Installed the Python SDK, inspected the client and embed signatures, and wrapped it in an embedder with separate document and query input types and batched document calls. I had no API key, so the live path is covered only by a test that skips without a key; everything else ran against a deterministic hash stand-in. The service itself was never exercised.
- What worked
- The client API is small and obvious: construct with a key, call embed with a list of texts, a model name and an input type. The document-versus-query distinction is explicit, which maps cleanly to indexing versus search. The error module was easy to enumerate for exception mapping.
- What got in the way
- The package pulls in a very large dependency tree for what is essentially a thin HTTP client: a LangChain core package, an async HTTP stack, a model-hub client and a tokenizer library among others, adding roughly fifty pins to a previously small requirements file. That is heavy enough that I offered to replace the SDK with a direct REST call.