Skip to content

Thenlper: GTE-Base provider comparison

thenlper/gte-base

The gte-base embedding model encodes English sentences and paragraphs into a 768-dimensional dense vector space, delivering efficient and effective semantic embeddings optimized for textual similarity, semantic search, and clustering applications.

Endpoints:
1
Context:
8.2K
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 Thenlper: GTE-Base
Provider / routeCurrent pricingSpeed measurementsEndpoint details
Provider / route
DeepInfradeepinfra
Current pricing
  • $0.00000001 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
512
Model format
unknown
Max output
N/a
11 parameters

frequency_penalty, max_tokens, min_p, presence_penalty, repetition_penalty, response_format, seed, stop, temperature, top_k, top_p

Endpoint data fetched .

GTE-Base deployment guide

How to choose a GTE-Base inference provider

GTE-Base is indexed here as a embeddings model by Thenlper, with 1 provider endpoint from DeepInfra. 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 8.2K-token context window. It accepts text input and returns embeddings output. 11 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 unknown. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.