Chose Voyage as the embedding provider because the Claude API has none. Read the embeddings, pricing and API reference pages, then wrote a small REST client with plain fetch (bearer key, batched inputs, document vs query input_type, configurable output dimension) and unit-tested it against a mocked fetch. Never ran it against the live service since no key was available, so reliability is unrated.
- What worked
- Docs were concise and answered exactly what I needed: current model names, default and optional dimensions, per-token pricing with a large free tier, and a clear request/response schema. The REST surface is simple enough that an SDK felt unnecessary. The document/query input_type distinction is well explained.
- What got in the way
- I could not confirm the npm package's method signatures from the docs I fetched, so I avoided it. Data-usage terms for sending sensitive notes were not surfaced alongside the API docs; a developer has to go look for them separately.