Request Path
Each chat completion request moves through a small number of systems. Lowertoken handles authentication, billing checks and routing. The selected upstream model provider processes the prompt and completion under its own terms.
api.lowertoken.com.Upstream Selection
Phase 1 prioritizes lower-cost domestic China-route capacity and labels it clearly. Provider regions, retention and training policies may vary by upstream account, endpoint and model family.
| Provider route | Model family | Preferred access posture | Launch status |
|---|---|---|---|
| Tencent TokenHub | DeepSeek, Kimi, MiniMax, Qwen, GLM, Hy3 | Primary prepaid China-route aggregator. Requests are sent to Tencent TokenHub and its selected upstream model route. | Primary live |
| DeepSeek official API | DeepSeek chat and reasoner | Official China-route endpoint kept as a direct specialist or fallback route. | Live |
| Alibaba Cloud Model Studio / DashScope | Qwen qwen3.6-plus | Current live route uses the DashScope endpoint. Treat this as a China-route provider until an Alibaba Cloud International account and region are enabled. | Live |
| SiliconFlow China | Aggregated efficient models | China-route aggregator used for long-tail coverage and fallback routing. | Live |
| Moonshot / Kimi China | Kimi | China-route endpoint kept for direct Kimi models and route comparison. | Live |
| Zhipu / GLM China | GLM | China-route endpoint kept for direct GLM models and fallback routing. | Live |
Retention and Training Use
Prompt bodies
Lowertoken does not intentionally persist prompt or completion bodies in application logs beyond transient buffers needed to stream the response. Prompt content is transmitted to the selected upstream provider to generate the response.
Request metadata
We retain operational metadata such as account, key, model, token counts, timestamps, status codes and billing events for abuse prevention, support and accounting.
Model training
Lowertoken does not use customer prompts to train models. Operational logs are designed to avoid prompt and completion text. Upstream providers may apply their own processing and retention practices.
Customer Controls
| Control | Phase 1 behavior | Team option |
|---|---|---|
| Provider allowlist | Public routes listed in console. | Manual allowlist review for teams. |
| Provider denylist | Model-level route selection. | Manual denylist review for sensitive workloads. |
| Usage limits | Per-key limits and prepaid balance. | Higher limits after manual review. |
| Data questions | Support through console contact. | Routing summary before production use. |
Data Requests
Customers can request account deletion, metadata export or routing clarification through the support contact published in the console. For regulated workloads, review upstream provider terms before sending production data.