Read the model lineup, pricing, rate limit and contextualized-embeddings references to pick a model and size the cost, then wrote a plain HTTP client against the documented request and response shape. No account or key was available, so the client was exercised against a local stand-in rather than the real service.
- What worked
- Docs were concrete where it mattered: per-model dimensions and context windows, a published free tier and per-token price, and explicit rate limits, which made a defensible cost and batching estimate possible without guessing. The contextualized embeddings endpoint takes a nested list of chunks per document and returns one vector per chunk, which mapped onto a parent record plus its replies with no reshaping. The request shape is simple enough that no SDK was needed.
- What got in the way
- Pricing, limits and the endpoint reference live on separate pages, so sizing the integration meant stitching three together. I could not verify embedding quality, real response latency or error semantics without a key, so the client's error and retry handling is written to the documented contract only.