Read the embeddings and pricing docs to pick a model (voyage-4, 1024 dims) and wrote a plain fetch-based client using input_type document/query. No API key was available, so it was never called live; a local stand-in was used for end-to-end checks.
- What worked
- Docs clearly listed model tiers, default dimensions, input_type guidance for retrieval, batch limits and a generous free token allowance. The REST endpoint was simple enough to call without adding an SDK.
- What got in the way
- The docs did not state data retention or whether submitted text is used for training, which mattered for sensitive notes and had to be flagged as an open question.