Qwen2.5 7B Instruct
Trusted Execution Environmentqwen/qwen-2.5-7b-instructModel weightsQwen2.5 7B is the latest series of Qwen large language models. Qwen2.5 brings the following improvements upon Qwen2:
-
Significantly more knowledge and has greatly improved capabilities in coding and mathematics, thanks to our specialized expert models in these domains.
-
Significant improvements in instruction following, generating long texts (over 8K tokens), understanding structured data (e.g, tables), and generating structured outputs especially JSON. More resilient to the diversity of system prompts, enhancing role-play implementation and condition-setting for chatbots.
-
Long-context Support up to 128K tokens and can generate up to 8K tokens.
-
Multilingual support for over 29 languages, including Chinese, English, French, Spanish, Portuguese, German, Italian, Russian, Japanese, Korean, Vietnamese, Thai, Arabic, and more.
Usage of this model is subject to Tongyi Qianwen LICENSE AGREEMENT.
- Modalities
- TexttoText
- In / out price
- $0.10 / $0.20per 1M
- Context
- 33K
- Released
- Oct 3, 2025
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.
 phala | Checking | Checking | Checking |
Start building
Call this model from your application, or through your agents.
For applications
Point your OpenAI SDK at the Gateway. Chat, completions, and embeddings work unchanged.
For agents
Connect Claude Code, Codex, Pi, and more through Private AI Proxy. Traffic is protected while a verified session is active.
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://tee.redpill.ai/v1",
apiKey: process.env.REDPILL_API_KEY,
});
const response = await client.chat.completions.create({
model: "qwen/qwen-2.5-7b-instruct",
messages: [{ role: "user", content: "Say hello." }],
});Check privacy evidence
Follow the receipt from the gateway response to its verified session using four curl requests.
- 1Check 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, ... }, ... }, ... } - 2Send a private request
The response header contains the receipt ID, not the receipt itself.
curl -fsS -i "https://tee.redpill.ai/v1/chat/completions" \ -H "Authorization: Bearer $REDPILL_API_KEY" --json '{"model":"qwen/qwen-2.5-7b-instruct","messages":[{"role":"user","content":"Hello"}],"provider":{"aci_verified":true}}'Output
HTTP/2 200 x-receipt-id: rcpt-e0eefe63b3673e2a5984951f ... { "model": "qwen/qwen-2.5-7b-instruct", ... } - 3Inspect 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:..." } ], ... } - 4Inspect 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", ... }, ... }, ... }