Skip to content

Perplexity: Embed V1 0.6B provider comparison

perplexity/pplx-embed-v1-0.6b

pplx-embed-v1-0.6B is one of Perplexity's state-of-the-art text embedding models built for real-world, web-scale retrieval. pplx-embed-v1 is optimized for standard dense text retrieval with the 0.6B parameter model targeting lightweight, low-latency...

Endpoints:
1
Context:
32K
Input:
text
Output:
embeddings

Visual comparison

Endpoint pricing chart

Compare published endpoint pricing visually.

Effective price by endpoint

USD per unit for prompt. Lower is better.

Only directly comparable published units are charted.

Server-rendered comparison

Provider endpoints

Prices are shown only in the units published by OpenRouter; cross-unit rankings are intentionally omitted. Missing speed data never removes an endpoint.

Endpoint comparison for Perplexity: Embed V1 0.6B
Provider / routeCurrent pricingSpeed measurementsEndpoint details
Provider / route
Perplexityperplexity/int8
Current pricing
  • $0 per unit (prompt)
  • Free per unit (completion)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
100.00%
Context
32K
Model format
int8
Max output
N/a
7 parameters

frequency_penalty, max_tokens, presence_penalty, temperature, top_k, top_p, web_search_options

Endpoint data fetched .

Embed V1 0.6B deployment guide

How to choose a Embed V1 0.6B inference provider

Embed V1 0.6B is indexed here as a embeddings model by Perplexity, with 1 provider endpoint from Perplexity. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.

Match the endpoint to the workload

The model publishes a 32K-token context window. It accepts text input and returns embeddings output. 7 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.

Compare embeddings billing units directly

At least one unit is published consistently across the listed endpoints, allowing a direct price chart for prompt. Other charges remain in the table using OpenRouter’s exact billing labels.

Verify route format and availability

Published endpoint formats include int8. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.