Publication confirms the /v1/embeddings route; it does not claim features the contract has not documented.
BAAI
AvailableBge Large Zh V1.5
API ID: BAAI/bge-large-zh-v1.5
BAAI is published through NexoRouter as an embedding model for semantic search, retrieval, clustering, and RAG workflows.
- Type
- Embedding
- Input / generation
- $0.00 / 1M tokens
- Output
- $0.00 / 1M tokens
- Endpoint
/v1/embeddings
Verified information
Overview
BAAI/bge-large-zh-v1.5 is presented as an embedding model from BAAI. Use it when your application needs vectors for retrieval, search, or semantic classification; confirm the exact parameters you will send in your application documentation.
The displayed price is NexoRouter's approved public price, not an internal cost or supplier discount.
Context, tools, benchmarks, latency, TTFT, and availability appear only when they have a source and measurement window.
Delivery contract
Provider & route
BAAI/bge-large-zh-v1.5 is exposed by NexoRouter under the verified BAAI catalog mapping below. This is the delivery contract customers should use, not a promise of additional upstream routes.
ProviderModel IDEndpointStatus
BAAI
BAAI/bge-large-zh-v1.5/v1/embeddingsAvailableProvider names describe the reviewed catalog mapping. NexoRouter does not claim multi-provider failover for a model unless it is measured and published separately.
Public billing
Pricing
Public usage pricing for this model ID. The unit changes by endpoint: not every model is billed by tokens.
- Input / generation
- $0.00 / 1M tokens
- Cached input
- —
- Output
- $0.00 / 1M tokens
Cost estimator
Estimate a request with the current public price for this exact model ID.
Estimated total$0.00
Estimate only. Actual usage, rounding, cached tokens, media parameters, and the final billing ledger determine the charged amount.
Prices are published after commercial review. A supplier update creates a review; it never exposes supplier discounts, orders, or internal costs.
Measured, not estimated
Performance
Performance metrics are published only after NexoRouter has enough model-specific production observations and a defined measurement window.
Tokens per second require streaming observations for this exact model ID.
A gateway response time is not the same as model inference latency, so the two are not mixed.
TTFT appears only when streaming timestamps are available for a representative sample.
No benchmark or chart is synthesized from another provider. These fields will populate only from NexoRouter measurements with a sample size and time window.
NexoRouter aggregate telemetry
Activity
Privacy-preserving, aggregate model activity from NexoRouter gateway logs. No prompts, API keys, user identities, or IP addresses are exposed.
More production observations are needed
This page waits for at least 10 aggregate attempts in the current seven-day window before publishing a success rate or traffic statistic.
Success rate is computed from NexoRouter gateway outcomes for this model ID. It is not an upstream SLA, quality score, or benchmark.
OpenAI-compatible
Integration
NexoRouter exposes this model through /v1/embeddings. Use a NexoRouter API key and retain the OpenAI-compatible base URL.
curl --fail-with-body 'https://api.nexorouter.com/v1/embeddings' \
-H "Authorization: Bearer $NEXOROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "BAAI/bge-large-zh-v1.5",
"input": "Text to embed"
}'Embeddings example using the exact model ID. Validate dimensions and normalization in your pipeline before indexing real data.
Start with the API reference
Open guideConfirm authentication, endpoint, request shape, and limits before copying an integration into production.
Provenance
Sources & updates
Every profile combines NexoRouter operating data with provider documentation links. A provider link does not become a capability promise until that claim is reviewed and published.
NexoRouter public catalog snapshot
Public route, availability, and price checked in the catalog snapshot: Aug 27, 2026, 12:52 AM UTC.
- NexoRouter catalogNexoRouter published catalogAug 27, 2026, 12:52 AM
- Official documentationBGE model documentationOpen source
Update policy: route evidence targets a 6 h cadence and official-document monitoring, when enabled in production, at least every 24 h. A change creates an internal proposal; claims and translations require human review and are revalidated within 30 days.
For developers
FAQ
What is BAAI/bge-large-zh-v1.5 for?
BAAI/bge-large-zh-v1.5 is published for embeddings, retrieval, and semantic search. Evaluate relevance and cost on your own data before using it as a production index.
What does BAAI/bge-large-zh-v1.5 cost?
The current public price is $0.00 / 1M tokens for input or generation and $0.00 / 1M tokens for output. The visible unit is the billing unit for this endpoint.
What is this model called in the API?
Use BAAI/bge-large-zh-v1.5 exactly as the model ID and call /v1/embeddings with a NexoRouter API key.
How is usage for this model billed?
NexoRouter records usage in the endpoint's public billing unit. The current published figures are $0.00 / 1M tokens for input or generation and $0.00 / 1M tokens for output; the billing page remains the account ledger.
How reliable is this model on NexoRouter?
NexoRouter has not yet reached the minimum public sample for this model in the current seven-day window. The page will publish aggregate reliability only after at least 10 attempts.
Why are benchmarks, context, or uptime not shown?
We do not publish figures without a verifiable source, method, and measurement window. When NexoRouter has aggregated telemetry and documentation for those fields, they will be added with their provenance.