Private Models

Qwen: Qwen3 Embedding 8B

Trusted Execution Environment
qwen/qwen3-embedding-8b
CompareGateway API

The Qwen3 Embedding model series is the latest proprietary model of the Qwen family, specifically designed for text embedding and ranking tasks. This series inherits the exceptional multilingual capabilities, long-text understanding, and reasoning skills of its foundational model. The Qwen3 Embedding series represents significant advancements in multiple text embedding and ranking tasks, including text retrieval, code retrieval, text classification, text clustering, and bitext mining.

Modalities
TexttoEmbeddings
Price
$0.01per 1M
Context
33K
Released
Jan 14, 2026

Providers

RedPill routes this private model across verified providers with automatic fallbacks. Pricing is unified, so you pay the same price no matter which provider serves your request, while live metrics show first-token latency, speed, and uptime.

chutesCheckingCheckingChecking

Gateway API

Generate embeddings with this model through RedPill's OpenAI-compatible API.

  1. Create an API key
  2. Set REDPILL_API_KEY
  3. Run the request
  4. Verify the response
Create keyDocumentation
Working with agentsConnect RedPill to agent frameworks and runtimes.
import OpenAI from "openai";

const client = new OpenAI({
  baseURL: "https://tee.redpill.ai/v1",
  apiKey: process.env.REDPILL_API_KEY,
});

const response = await client.embeddings.create({
  model: "qwen/qwen3-embedding-8b",
  input: "Private AI keeps prompts confidential.",
});

Check privacy evidence

Follow the receipt from the gateway response to its verified session using four curl requests.

  1. 1
    Check the gateway

    Fetch the current TEE evidence and check that the keyset has not expired.

    curl -fsS "https://tee.redpill.ai/v1/aci/attestation" \
  -H "Authorization: Bearer $REDPILL_API_KEY"

    Output

    {
  "api_version": "aci/1",
  "workload_keyset_digest": "sha256:4f3dc45e...",
  "attestation": { "workload_keyset": { "not_after": 1790498751, ... }, ... },
  ...
}
  2. 2
    Send a private request

    The response header contains the receipt ID, not the receipt itself.

    curl -fsS -i "https://tee.redpill.ai/v1/embeddings" \
  -H "Authorization: Bearer $REDPILL_API_KEY" --json '{"model":"qwen/qwen3-embedding-8b","input":"Hello","provider":{"aci_verified":true}}'

    Output

    HTTP/2 200
x-receipt-id: rcpt-e0eefe63b3673e2a5984951f
...

{
  "model": "qwen/qwen3-embedding-8b",
  ...
}
  3. 3
    Inspect the receipt

    Paste the x-receipt-id above and compare its keyset digest with step 1.

    curl -fsS "https://tee.redpill.ai/v1/aci/receipts/REPLACE_WITH_RECEIPT_ID" \
  -H "Authorization: Bearer $REDPILL_API_KEY"

    Output

    {
  "api_version": "aci/1",
  "receipt_id": "rcpt-e0eefe63b3673e2a5984951f",
  "workload_keyset_digest": "sha256:4f3dc45e...",
  "event_log": [
    ...,
    { "type": "upstream.verified", "session_id": "63c5a08de14e5c5253e6fb29271151f40621beb83b552ccca65772772856053f", "result": "verified", "required": true },
    { "type": "response.returned", "body_hash": "sha256:..." }
  ],
  ...
}
  4. 4
    Inspect the session

    Copy session_id from the upstream.verified event above, then fetch that session.

    curl -fsS "https://tee.redpill.ai/v1/aci/sessions/PASTE_SESSION_ID_FROM_RECEIPT" \
  -H "Authorization: Bearer $REDPILL_API_KEY"

    Output

    {
  "api_version": "aci/1",
  "upstream_name": "...",
  "verifier_id": "...",
  "claims": { "tee_attested": { "status": "asserted", ... }, ... },
  ...
}
Full cryptographic verification guide

Search

Search models and pages.