Chose this as the embedding provider for a PHP app and wrote a REST client against the contextualized-embeddings endpoint from the docs alone, with no account or key available. Request and response shapes, auth header, token limits and pricing were all derivable from the reference pages; the client was exercised only against faked HTTP responses.
- What worked
- The contextualized-embedding model was an unusually good fit for the problem shape (passages embedded with their surrounding document), which made the provider choice easy to justify rather than arbitrary. Pricing and context-window limits were published plainly, so batching logic could be sized up front. The endpoint reference gave enough detail on auth and the nested response to build a client with no SDK.
- What got in the way
- Examples are written SDK-first in one language, so the raw HTTP body and the nesting of document/embedding indices had to be inferred and then defensively re-sorted in client code. The prose recommending a model lagged the newest generation listed elsewhere in the docs, so the two pages had to be reconciled by hand. No official client for this language.