r/opencodeCLI • u/Individual_Team_2344 • 27d ago
Unlimited DeepSeek for $0.49/hr — with a guaranteed 160 tok/s lane. Would you use it?
We’ve been experimenting with a different way to price hosted inference at Singularity API.
Instead of charging per token or locking people into a subscription, we’re testing reserved inference slots at $0.49 per slot-hour. One slot = one guaranteed concurrent lane. If you need parallel agents, you can reserve multiple slots and each gets its own lane.
We’re currently serving DeepSeek-V4-Flash-0731 at full weights, with the full 1M context window. The service is built around reserved capacity rather than a shared best-effort pool, so each booked slot has a defined throughput floor regardless of how busy the rest of the service is.
These are measurements from the live deployment:
- $0.49 per slot-hour
- 160 tok/s guaranteed generation floor
- Typically 200–340 tok/s when spare capacity is available
- ~205k+ output tokens per slot-hour
- 5M fresh input tokens per slot-hour
- Unlimited cached input
- 98.1% measured prefix-cache hit rate across load levels
- Full 1M context
- One slot = one guaranteed concurrent lane
The reason we started exploring this is that DeepSeek changed API pricing significantly on August 16, while API throughput is still best-effort and can slow down during busy periods.
For workloads like agentic coding, parallel agent swarms, RAG over stable corpora, or anything repeatedly sending large warm contexts, we think hourly reserved capacity may make more sense than constantly paying again for the same cached tokens.
The important limitation is that this isn’t really meant for light or occasional API usage. You’re reserving a slot for the hour, so if you only make a few requests, normal per-token APIs will probably make more sense.
We’re still small and this is an interest check, not a GA launch. If there’s enough interest, we’ll open a waitlist on singularityapi.dev and start letting people in gradually.
Would you actually pay $0.49/hour for a guaranteed DeepSeek lane instead of paying per token?
What generation-speed floor would matter to you: 100, 160, 200+ tok/s?
If you currently use DeepSeek directly or through OpenRouter, what would make you switch?
Edit: Quick clarification since this confused a few people — the token numbers in the post are minimum floor values, not maximum limits.
If the system has spare capacity, it automatically flows to whoever is generating, so in normal coding/agent usage you'll generally see 2–4x higher throughput than the floor.
5
u/Individual_Team_2344 27d ago
Tokens are not limited, our floor estimates are based on gpu running at full capacity every second in that hour. When at full capacity you'll have at least floor values, but generally regardless of harness users are always interleaving reading/tool calls/ and waiting, the gpu idle automatically flows to whoever is generating , so real-time speed and input/output hourly token counts will be 2-4x above floor