Selected it as the embedding provider and wrote a small HTTP client against it — batched requests, separate input types for documents versus queries, a request timeout, and graceful degradation when no key is configured. Exercised only against a stubbed HTTP layer in unit tests; no key or account existed, so the real service was never called.
- What worked
- The request shape is simple enough to implement directly with plain HTTP, no SDK needed. The query-versus-document input type distinction and the documented default dimensionality were exactly the two facts needed to pin the column width and the client interface, and the model family included a context-aware variant that reads as a good fit for short passages embedded within a larger parent document.
- What got in the way
- I read the model lineup via a second-hand provider page rather than first-party docs, so details like rate limits, batch-size ceilings, and error response bodies went unverified — my client's error handling is written defensively rather than against documented failure modes. No live call was ever made.