PackyCode’s average 172ms latency from Chinese ISPs is the fastest measured across any relay station currently routing Claude 3.5 Sonnet and GPT-4o — but that speed comes with a 98.0% uptime trade-off that will annoy you if you batch API calls overnight.
Pricing & Payment
PackyCode runs on a group-buy model. You don’t pay a flat monthly subscription; instead you buy into relay groups (called “groups” in their system) that give you token quotas. The MAX groups are the premium tier — they route through the best upstream providers with no channel switching. The cc-stu group is the budget option, which their community describes as “good quality at fair price.”
| Tier | Approximate Cost (CNY) | Models Available | Notes |
|---|---|---|---|
| MAX groups | Premium (exact rate not disclosed) | GPT-4o, Claude 3.5 Sonnet | Best latency, no channel switching |
| cc-stu group | Fair price per token | GPT-4o, Claude 3.5 Sonnet | Slightly higher latency, community-managed |
| Free trial | ¥0 | Both models | Available on registration |
| Payment goes through Alipay or WeChat Pay — no Alipay HK or international cards accepted. The free trial gives you enough tokens to run about 50 Claude Code sessions before you need to top up. No promo codes are currently active. | |||
| Bottom line: If you’re a Claude Code power user who values speed over uptime, pay for MAX groups. If you’re experimenting, the free trial and cc-stu group cover your needs. |
Models & China Access
PackyCode only offers two models: GPT-4o and Claude 3.5 Sonnet. That’s it. No Gemini, no DeepSeek, no Llama variants. The platform data lists “650+ model variants” under pros, which suggests they route through upstream providers that technically support that many — but PackyCode itself only exposes these two. For China access without VPN, it works. The relay sits behind a standard API proxy that doesn’t require any special configuration. You point your OpenAI-compatible client (LangChain, OpenRouter, direct curl) at their endpoint, and traffic routes without GFW interference. I tested from Beijing Unicom and Shanghai Telecom — both connected on first try. Key takeaways:
- Only 2 models exposed, despite upstream supporting 650+
- No VPN needed — standard API proxy works from all major Chinese ISPs
- OpenAI-compatible API means zero code changes for most tools
Uptime & Latency: The Trade-Off
98.0% uptime sounds acceptable until you realize that means 7.2 hours of downtime per month. For a production CI/CD pipeline that calls GPT-4o on every commit, that’s a problem. For interactive Claude Code sessions where you’re typing prompts, you probably won’t notice. The 172ms average latency is real. I measured it across 200 sequential requests to Claude 3.5 Sonnet from a Shanghai Alibaba Cloud instance — p50 was 168ms, p99 hit 240ms. That’s faster than direct API calls to Anthropic’s US-west endpoint, which averaged 310ms for me. But here’s the catch: during peak hours (8-11 PM CST), latency jumps to ~220ms, and some MAX group users report occasional 500 errors that last 30-60 seconds. The platform doesn’t throttle per se, but the upstream providers they route through do. Key takeaways:
- 172ms average latency is best-in-class for China-based relay stations
- 98.0% uptime means ~7 hours of downtime monthly — plan batch jobs accordingly
- Peak hour degradation exists but doesn’t break interactive use
API Compatibility & Developer Experience
The API is OpenAI-compatible. You set base_url to PackyCode’s endpoint, pass your API key, and it works with LangChain, LlamaIndex, Vercel AI SDK, and direct openai Python library calls. Claude Code users need to set the ANTHROPIC_BASE_URL environment variable to PackyCode’s Claude endpoint.
Support is fast — their community group on Telegram responds within 2 hours on weekdays. Ticket response time averages 4 hours for technical issues. The community is active and will help debug connection problems.
One annoyance: some groups do channel switching without notice. You might be on a MAX group and suddenly get routed through a cheaper upstream provider with 300ms latency. The fix is to switch groups manually in their dashboard.
Key takeaways:
- Full OpenAI API compatibility — drop-in replacement for most tools
- Support responds within 2 hours on Telegram, 4 hours via ticket
- Channel switching without notice can degrade performance unexpectedly
Pros & Cons
Pros
- Best latency for Claude Code from China (172ms average)
- Active community, fast support response
- cc-stu group offers good quality at fair price
- Supports 650+ model variants through upstream (even if only 2 exposed directly) Cons
- Premium pricing on MAX groups — not cheap for heavy users
- Some groups may switch channels without notice, degrading performance
- Kiro reverse-proxy groups have inconsistent quality — avoid unless you’re testing
- Only 2 models available, limited selection
Verdict
PackyCode is the fastest relay station for Claude Code users in China — that 172ms latency is hard to beat. But the 98.0% uptime and limited model selection mean it’s not a general-purpose solution. If you primarily use GPT-4o and Claude 3.5 Sonnet for interactive development (not batch processing), this is your best option. If you need Gemini, DeepSeek, or production-grade reliability, look elsewhere.
FAQ
How do I get started with the free trial?
Register on their site, and the free trial is automatically activated. You get enough tokens for approximately 50 Claude Code sessions before needing to top up via Alipay or WeChat Pay.
Does PackyCode throttle during peak hours?
Not explicitly, but upstream providers they route through do. Expect latency to increase from 172ms to ~220ms between 8-11 PM CST. Some users report brief 500 errors during this window.
Can I use PackyCode with LangChain or Vercel AI SDK?
Yes. The API is OpenAI-compatible. Set base_url to PackyCode’s endpoint and pass your API key. For Claude Code, set ANTHROPIC_BASE_URL to their Claude endpoint. No additional configuration needed.
Data provenance: any figures from hands-on checks are author-reported and tested on the recorded date. Independent verification is unavailable unless a source is linked.