Discussions
REST API for connectivity/health checks
Hi, is there an endpoint, e.g. HEAD / that will simply respond 200/OK if it's alive?
The server is overloaded or not ready yet
Hello, i am experiencing this issue, please kindly help.
Other languages for law and legal texts
What about Turkish?
service timeout
service timeout on utc time today 00:30 am, what`s wrong?
the service department is unstable these days.
the same text but return the different vectors
we called the same text "hello" but give different result on index : 0. Is it expected?
curl --location --request POST 'https://api.voyageai.com/v1/embeddings'
--header 'Authorization: Bearer --'
--header 'Content-Type: application/json'
--data-raw '{
"model":"voyage-large-2",
"input":["hello"]
}'
Opt out of training with customer data?
Voyage AI terms of services mentioned opt-out functionality on the Website, but I can't find it on API Keys, Profile, etc. It says unless I opt out, Voyage AI could use customer data for training?
rate limit now is of 20.0 requests per minute ?not 300 per minute
errr :{"detail":"You have exceeded your Requests Per Minute (RPM) rate limit of 20.0 requests per minute. To prevent further rate limiting, try exponential backoff or sleeping between requests as described in our documentation, or try sending requests with larger batch sizes. If you would like a higher RPM}
Error: The server is overloaded or not ready yet.
Hi,
Top up account
Hi
Unicode character support
We're evaluating using voyage to generate embeddings for later use in semantic search, but it appears that at least some unicode characters are not supported and cause the embedding API call to return 400 errors: {"detail":"There was an error parsing the body"}, for example Pyrex Spring Blossom Light Green Beaded Edge Nested Mixing Bowl 402 1 ½ Qt fails but Pyrex Spring Blossom Light Green Beaded Edge Nested Mixing Bowl 402 1 Qt succeeds. The same code framework succeeds for both inputs using gemini's text embedding API, so the basic handling of HTTP requests, content types and encodings is correct (the input is JSON encoded in utf-8, which is the assumed encoding for type application/json, and declaring it explicitly in the content-type does not change the behaviour).