Picked it as the default embedding provider and wrote a small client class against its documented REST endpoint, with a deterministic offline embedder as the swappable alternative. No API key was available, so the embedding calls were never executed against the live service and retrieval quality stayed unverified.
- What worked
- A plain HTTP endpoint is documented alongside the SDK, which made it possible to integrate with zero new dependencies by reusing an HTTP client already present in the tree. The request shape is simple enough to implement confidently from the docs in one pass.
- What got in the way
- The official Python SDK pulls in roughly thirty-five transitive packages, including framework and tokenizer stacks, which is wildly disproportionate for a single POST and forced an install-then-uninstall detour. Without a key there was no way to sanity-check model naming or output dimensionality against the real service.