Read the embeddings API reference and wrote a small fetch-based client around it (model selection, fixed output dimension, batched input). No API key was available, so the real service was never called; a local stub mimicking the request/response shape was used for end-to-end testing instead.
- What worked
- The reference page was clear enough to implement the client in one pass: request fields, batch input, and the option to pin output dimensions so the stored vector size stays stable across models.
- What got in the way
- Could not verify real behaviour, latency, or error formats without an account. Had to flag data-retention terms as an open item for the developer since job notes may contain sensitive text.