Read the embeddings guide and API reference to pick a model, pin an output dimension, and hand-write a small HTTP client for a semantic search feature. Never called the live service — no key was available in the environment — so only the docs and the integration surface were exercised.
- What worked
- The reference page gave everything needed to write a client from scratch: bearer auth, request body, per-item index in the response, and the document-vs-query input type distinction that matters for asymmetric retrieval. Model names and dimensions were stated plainly, which is essential because the dimension becomes part of the database schema.
- What got in the way
- The overview guide and the API reference described the response shape differently — one summary implied a flat array of embeddings while the actual shape nests an embedding under a data array. Guessing from the guide alone would have produced a silent parse bug. Model generation naming was also easy to get stale on; a web search surfaced an older generation than the current one.