LogoLMSpeed
  • Home
  • Free
  • Models
  • Providers
  • Docs
LogoLMSpeed
LogoLMSpeed

The best API speed test tool

GitHubGitHubTwitterX (Twitter)Email
Product
  • Features
  • Pricing
  • FAQ
Leaderboard
  • Overview
  • Speed Ranking
  • Latency Ranking
  • Health Ranking
  • Model Pricing
  • Model Speed
  • Reasoning
  • Coding
Models
  • All Models
  • GPT
  • Claude
  • Gemini
  • DeepSeek
  • Llama
  • Qwen
Free Models
  • All Free Models
  • Free GPT
  • Free Claude
  • Free Gemini
  • Free DeepSeek
  • Free Llama
  • Free Qwen
Resources
  • Speed Test
  • Provider Directory
  • Documentation
Legal
  • Cookie Policy
  • Privacy Policy
  • Terms of Service
© 2026 LMSpeed All Rights Reserved.Made by Nexmoe with ❤️

CLIPROXYAPI

cpa.tongxin.de

LMSpeed tracks CLIPROXYAPI API pricing, model coverage, speed tests, and uptime signals for cpa.tongxin.de.

CLIPROXYAPI provides a management interface for CLI proxy API services, enabling configuration and access control.

OpenAIGPT-5.4

CLIPROXYAPI offers 6 LLM API models.

Speed benchmark average: 59 tok/s.

CLIPROXYAPI interface preview
OverviewPerformance6HealthEmbed
Avg Speed59.26 tok/s
Latency8.63 s
Updated6/10/2026
Created At4/18/2026
Website

API Endpoints

  • cpa.tongxin.de

Data as of Jun 10, 2026, 09:24 AM·Rankings are based on community-submitted tests and periodic health probes. Advisory only, not official data.

Healthy
Last checked 6/10/2026, 12:20:04 PM
Latency
3672ms
Day
100%
Recent availability
Week
100%
Recent availability
Month
100%
Recent availability
Latency
3159ms
7d avg: 3159ms

Health Check

5History (5 pts)
PastNow

Health history

TimeStatusHourly uptimeLatency
2026-06-105/5100%3159ms

Recent Incidents

No incidents reported recently

Health Check Rules

  • Check target: the provider's dedicated health check URL, or its website URL as fallback.
  • Request method: HTTP GET with automatic redirect following.
  • Healthy criteria: HTTP status code 200–399 is considered healthy; any other status or network error is unhealthy.
  • Timeout: each check has a 5-second timeout. If the server does not respond within 5 s, the check is marked as failed.
  • Frequency: health checks run periodically via an automated cron job for all providers.