Model detail
Embed Multilingual v3.0
Provides multilingual classification and embedding support. See supported languages here.
Model specs
- Model ID
-
embed-multilingual-v3.0
- Context length
- 512
- Max output
- –
- I/O modalities
- Released
- 2023-11
02
API endpoints
One MixRoute gateway, OpenAI-compatible
-
OpenAI-compatible
/v1/chat/completionsPOST
03
Pricing
Flat rate, unit: /1M Tokens
Input
$0.1000 /1M Tokens
Completion
$0.1000 /1M Tokens
05
Selection summary
Quickly judge whether it fits your workload
What is this model good for?
Provides multilingual classification and embedding support
Provides multilingual classification and embedding support. See supported languages here.
What should you check before using it?
512 context tokens
Cohere model that supports vision input.
Why use it through MixRoute?
embed-multilingual-v3.0 takes text and images on one route
Text and image inputs share the same route and the same key. MixRoute serves embed-multilingual-v3.0 on the OpenAI-compatible endpoint /v1/chat/completions; point your existing client at https://api.mixroute.ai/v1 with the model ID embed-multilingual-v3.0 and re-run your integration tests.
07
Capabilities & compatibility
Unconfirmed capabilities stay "Unknown," no guesses
Vision input
embed-multilingual-v3.0 can process image inputs alongside text.
image_url content part alongside text messages.
OpenAI SDK
Call embed-multilingual-v3.0 through MixRoute's OpenAI-compatible endpoint.
base_url to https://api.mixroute.ai/v1; everything else follows the OpenAI style.
08
Token cost estimator
Live estimate from this page's pricing, not an actual bill
This model has no cache-read price; caching is not counted
09
FAQ
Before switching production traffic to Embed Multilingual v3.0, run a pilot on a representative slice of your traffic and check output quality, latency at peak concurrency, and cost per request. Verify the error and retry behaviour, and confirm the request limits you depend on match your plan.
One endpoint, a testable decision
Test this model and alternate routes with the same request format
Start from a real workload, then let quality, total cost, and failure conditions decide whether to send production traffic.