LFM2.5-Embedding-350M is a text embedding model from Liquid AI. It produces 1,024-dimensional embeddings for retrieval and semantic search.
Successful OpenRouter requests and embeddings may be retained and used to train Liquid models.
Modalities
Price
Free
Context
512
Released
Aug 18, 2026
This model is hosted by one provider. OpenRouter forwards every request to it directly — no routing decisions to make.
Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).
Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.
Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.
Token volume and request traffic to this model over time.
Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.
LFM2.5-Embedding-350M is a text embedding model from Liquid AI. It produces 1,024-dimensional embeddings for retrieval and semantic search. Successful OpenRouter requests and embeddings may be retained and used to train Liquid models.
Yes. The pricing shown on this page for LFM2.5-Embedding-350M (free) is zero, so you are not charged for embedded tokens. Free endpoints are rate limited — see the rate limit docs.
LFM2.5-Embedding-350M (free) accepts up to 512 tokens per input. Longer text has to be split into multiple inputs.
LFM2.5-Embedding-350M (free) accepts text as input and returns embedding vectors.
LFM2.5-Embedding-350M (free) was released on August 18, 2026.
| Free | -- |
99.84%
99.84%
When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and customization options.