Read the pricing page and the embeddings API reference to pick a model, output dimension and input_type hints, then wrote a plain fetch wrapper with unit-tested request/response helpers. Never called the live endpoint because no key was available; reliability unassessed.
- What worked
- Pricing page was explicit per model and clearly stated the free token allowance, which made the cost argument for a small nonprofit easy. The API reference documented the request body, the document/query input_type distinction, configurable output dimensions and the index field on each result, so building the client without an SDK was straightforward.
- What got in the way
- Had to confirm details by fetching docs rather than relying on memory; no observed behavior for rate limiting or error payloads, so 429 handling in the wrapper was written from the docs alone.