Feature comparison
All data verified April 2026. Prices in USD per million tokens.
| XinoAPI | OpenRouter | LiteLLM (self-hosted) | Direct (DeepSeek/etc) | |
|---|---|---|---|---|
| Pricing model | Published per-model rates; 3 featured models at 10% below the comparable Baidu Qianfan International list rate | 0% markup + 5.5% on credit purchase | Self-hosted (infra cost only) | Provider's native price |
| KYC required | No | No | You set policy | Yes (Chinese phone / ID) |
| Chinese models | 5 providers, all latest | Some, via aggregators | Bring your own keys | 1 provider per API key |
| Unified billing | Yes | Yes | No (per-provider) | No |
| OpenAI SDK compatible | Yes | Yes | Yes | Most (not all) |
| Client-side PII redaction SDK | Included | No | No | No |
| Response integrity (HMAC signing) | Yes | No | No | No |
| Audit log (hash-chained) | Yes | Usage only | Self-configured | Usage only |
| Streaming (SSE) | Yes | Yes | Yes | Yes |
| Failover / fallback routing | Yes | Yes | Yes | N/A |
| Free tier on signup | $2.00 credits | Rate-limited free models | N/A | Varies by provider |
| Payment methods | Card, Stripe | Card, alternative methods | N/A | Alipay, WeChat, Card |
| Open source | SDK only | No | Yes | No |
Price comparison
USD per million tokens. XinoAPI adds no separate top-up fee. Reference prices are from Baidu Qianfan International.
| Model | Baidu intl. list | XinoAPI | Savings |
|---|---|---|---|
| DeepSeek V4-Flash input | $0.140 | $0.126 | 10% |
| DeepSeek V4-Flash cache hit | $0.028 | $0.0252 | 10% |
| DeepSeek V4-Flash output | $0.280 | $0.252 | 10% |
| DeepSeek V4-Pro input | $1.690 | $1.521 | 10% |
| DeepSeek V4-Pro cache hit | $0.140 | $0.126 | 10% |
| DeepSeek V4-Pro output | $3.380 | $3.042 | 10% |
| GLM-5.2 input | $1.400 | $1.260 | 10% |
| GLM-5.2 cache hit | $0.260 | $0.234 | 10% |
| GLM-5.2 output | $4.400 | $3.960 | 10% |
Reference: Baidu Qianfan International price list, published September 7, 2026 and verified September 17, 2026. Compare the same model version, billing item, and route.
Latency comparison
Time to first token (TTFT), measured from Singapore, April 2026. Averaged over 100 requests per model.
| Model | XinoAPI (Singapore) | OpenRouter | Direct provider |
|---|---|---|---|
| DeepSeek V4-Flash | 180ms | 320ms | 140ms (from CN only) |
| Qwen 3.6 Plus | 160ms | 285ms | 120ms (from CN only) |
| GLM-5 | 210ms | 355ms | 150ms (from CN only) |
| Kimi K2.6 | 195ms | 410ms | 145ms (from CN only) |
| MiniMax M3 | 230ms | Not available | 180ms (from CN only) |
Direct provider latency is measured from mainland China. Accessing these same providers from outside China without a VPN typically fails entirely or adds 500ms+ of routing overhead.
Which one should you pick?
Match your situation to the right choice.
XinoAPI PICK
You primarily use Chinese LLMs and are based outside China.
- Need DeepSeek, Qwen, GLM, Kimi, or MiniMax as main workload
- Can't or don't want to complete Chinese KYC (phone, ID)
- Want PII redaction or response integrity signing out of the box
- Building agent workflows and concerned about router integrity (see arXiv:2604.08407)
- Want one bill, one API key, five providers
OpenRouter
Primarily OpenAI/Anthropic/Google, occasional Chinese access.
- Main workload is GPT-5, Claude, or Gemini
- Need access to 200+ models including niche open-weight
- OK with 2-3 hop routing for Chinese models (plaintext exposure)
- Value zero token markup over latency optimization
LiteLLM (self-hosted)
Enterprise with existing keys and infrastructure team.
- Have existing contracts with each provider
- Can dedicate 1 engineer to ops / maintenance
- Need custom routing logic or region pinning
- Regulated industry requiring on-prem data handling
- Willing to own security patches (March 2026 dependency confusion)
Direct provider APIs
Mainland China user, single model, maximum latency sensitivity.
- Based in China with local payment methods
- Using only one model, no multi-model routing needed
- Can complete Chinese KYC without issues
- Every millisecond of latency matters
- Don't need audit logs or PII redaction
Migration
All comparison options use the OpenAI SDK format. Switching is typically one line of code.
From OpenRouter to XinoAPI
from openai import OpenAI # Before client = OpenAI( api_key="sk-or-...", base_url="https://openrouter.ai/api/v1" ) # After client = OpenAI( api_key="xino-...", base_url="https://api.xinoapi.com/v1" ) # Model names: # openrouter → "deepseek/deepseek-v4-flash" # xinoapi → "deepseek-v4-flash"
From direct DeepSeek to XinoAPI
from openai import OpenAI # Before — only DeepSeek, Chinese KYC required client = OpenAI( api_key="sk-...", base_url="https://api.deepseek.com" ) # After — 5 providers, self-service onboarding, one bill client = OpenAI( api_key="xino-...", base_url="https://api.xinoapi.com/v1" ) # Use explicit model IDs: "deepseek-v4-flash", "deepseek-v4-pro" # Plus you now have access to: qwen-plus, glm-5.2, kimi-k3, MiniMax-M3
Frequently asked questions
Is XinoAPI cheaper than OpenRouter?
It depends on the model and route. DeepSeek V4-Flash, DeepSeek V4-Pro, and GLM-5.2 are currently 10% below the comparable Baidu Qianfan International list rate, and XinoAPI adds no separate top-up fee. Compare final per-model rates and purchase fees for your workload.
Can I use XinoAPI as a drop-in replacement for the OpenAI SDK?
Yes. The endpoint is OpenAI-compatible — change base_url to https://api.xinoapi.com/v1 and use your XinoAPI key. No other code changes required. Works with OpenAI Python, Node.js, and Go SDKs.
Does OpenRouter have DeepSeek, Qwen, and GLM?
OpenRouter has DeepSeek models via various aggregators, but its Qwen and GLM coverage is limited. For all five major Chinese models (DeepSeek, Qwen, GLM, Kimi, MiniMax) under one API key, you need XinoAPI or self-hosted LiteLLM with your own provider contracts.
How do I access DeepSeek API from outside China?
For supported regions, XinoAPI provides an OpenAI-compatible gateway to DeepSeek and other Chinese model families through one API key. Direct provider onboarding, verification, payment support, and regional availability vary by provider.
What is the safest way to use Chinese LLM APIs?
The 2026 study on malicious LLM routers highlights practical router risks such as payload injection and credential exposure. Defense: reduce prompt secrets, use client-side scanning/redaction, review agent tool calls, and prefer gateways with transparent security controls. XinoAPI provides privacy tooling and gateway controls for this workflow.
Does OpenRouter offer streaming (SSE)?
Yes, OpenRouter, XinoAPI, LiteLLM, and all major direct providers support SSE streaming. Set stream=true in your request and handle the event stream as you would with the OpenAI SDK.
Why does self-hosted LiteLLM show "Self-hosted" for pricing?
LiteLLM is open-source software you run on your own infrastructure. There's no per-token fee to LiteLLM itself — you pay whatever the underlying providers charge you directly, plus your infra cost (typically $30-100/month for a single VM). The tradeoff is you own ops, security patches, and scaling.
Can I migrate from one to another without code changes?
Yes, in most cases only the base_url and api_key change. Model names differ slightly — OpenRouter uses provider/model format (e.g., deepseek/deepseek-v4-flash) while XinoAPI and direct APIs use the bare model name (deepseek-v4-flash). A quick sed replacement usually suffices.
Which provider is best for agent workflows (Claude Code, Cursor, Codex)?
For Chinese models in agent contexts, the main risk is tool-call injection by malicious intermediaries. XinoAPI ships response signing + threat scanning specifically to defend agent workflows. Direct providers have the lowest hop count (highest security) but require you to be in China. OpenRouter's multi-hop architecture introduces risk — if any hop in the chain is compromised, tool calls can be rewritten. For production agent workloads, XinoAPI or direct APIs are the safer choices.
Try XinoAPI with $2 free credits
5 Chinese LLMs, one API key, self-service onboarding. Takes 2 minutes to get your first response.