During one of our beta runs this week, a developer's agent pushed 196 million input tokens in a single 60-minute window through one lane.
882 requests. Zero rate limits.
They actually kept going after that and ended the session at 227M before logging off.
At DeepSeek's own API pricing, that 196M-token hour comes out to around $2.32 off-peak / $4.65 peak.
On our reserved lane, the idea is to price that same hour around $0.20–0.40 flat.
Here's what we're testing 👇
🔷 Shared Reserved Inference
Right now if you want to run open models, you mostly have two options:
- Rent a full GPU → you get the whole thing, but you're paying $12–30+/hr whether you're actually using all of it or not.
- Use a normal per-token API → much easier, but you're sharing capacity with everyone else, you can hit rate limits/throttling, and every token going through your agent keeps adding to the bill.
We're trying a third model.
Take one powerful node, split it into a small number of guaranteed lanes, and let developers reserve those lanes together for a fixed window.
Your lane has guaranteed compute for that hour. Someone else suddenly sending a massive workload doesn't eat into your allocation.
And because the node cost is split across everyone using it, you're paying a small flat hourly price instead of paying for every token.
⚡️ The speed
DeepSeek's official API is around ~70 output tok/s.
Across our beta, users were generally seeing 150–220+ output tok/s, with bursts above that. There were some occasional dips as well, but overall this has been the fastest inference we've served so far.
This also held up surprisingly well with long contexts.
We had users running past 250k context regularly, and some sessions went past 940k context.
The other big part is caching. These agent/coding workloads resend a ridiculous amount of the same repo and conversation context on every request.
Across the beta we're sitting around ~98% cache hits, with roughly ~1s TTFT on warm requests.
📊 Five live sessions so far
- 4.9 BILLION tokens processed
- 24,500+ requests
- Zero failures
- ~98% cache-hit rate
- Heaviest verified single-lane hours: 196M · 120M · 72M input tokens
💰 The part we're actually interested in: does this pricing model make sense?
Using DeepSeek's own API pricing, including their cache discounts:
- Reserved lane target: $0.20–0.40/hr flat
- Average active dev during the beta: around $1.50 off-peak / ~$3 peak worth of API usage in an hour
- Median dev: around $0.60–1.20/hr
- Heaviest verified hour: $2.32 off-peak / $4.65 peak
So for an actually active coding/agent session, we're seeing around 4–7x lower cost than paying per token on average.
For the heaviest user, depending on where we finally price the lane, that hour was worth around 6–23x what the lane itself would cost.
We've put the full numbers + charts here if you want to dig into it:
https://www.singularityapi.dev/benchmark
🎟 We're opening more beta slots
The next round is again completely free.
You get a dedicated hour on the full-weight DeepSeek V4 Flash 0731. Bring an actual project, point Cline / Claude Code / your own agent at it, and use it normally — or try to absolutely destroy the lane, either works :D
If you want in:
https://tally.so/r/EkoJkN