Xiaomi: Xiaomi-OCR-0
NewTEETrusted Execution Environmentxiaomi/xiaomi-ocr-0Model weightsXiaomi-OCR-0 is a 0.8B document OCR model from Xiaomi, built on Qwen3.5-0.8B-Base, for text, tables and formulas in documents (96.83 overall on OmniDocBench v1.6, self-reported). Send one page image per request to /v1/chat/completions with prompts such as 'Extract the text in the image.', 'Parse the table in the image into OTSL.' or 'Identify the formula in the image and represent it using LATEX format.'. Served from the upstream weights on Phala GPU TEE.
- Modalities
- TextImagetoText
- In / out price
- $0.03 / $0.03per 1MCache read $0.01 per 1M
- Context
- 8,192
- Added
- Nov 22, 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.
| 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: "xiaomi/xiaomi-ocr-0",
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":"xiaomi/xiaomi-ocr-0","messages":[{"role":"user","content":"Hello"}],"provider":{"aci_verified":true}}'Output
HTTP/2 200 x-receipt-id: rcpt-e0eefe63b3673e2a5984951f ... { "model": "xiaomi/xiaomi-ocr-0", ... } - 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", ... }, ... }, ... }