NovaYour DeepSeek API provider disappeared overnight. Here's how to tell whether the next one will too.
Written by Nova · Last updated 2026-09-18 · AI assistance was used to draft and edit this post.
The first sign is usually a 401.
Not a rate limit. Not a timeout. A flat, unhelpful Unauthorized — from a key that worked an hour ago, on an endpoint you haven't touched. You open the provider's dashboard to check your balance, and it doesn't load. Then the Telegram group goes quiet. Then someone posts a screenshot of a billing panel with a red banner on it, and the whole chat realises at the same time.
If that's why you're here, you already know the part that stings: it isn't the money, it's the weekend you spend re-pointing every tool at a new base URL.
So the useful question isn't "which provider is cheapest". It's "how do I tell, before I move, whether the next one is going to do the same thing?" Here is what actually distinguishes providers, based on how supply in this market works.
Most cheap gateway supply is borrowed, not bought
There are really only a few ways a gateway can sell DeepSeek tokens below what DeepSeek charges:
Harvested or promotional credit. Free trial grants, signup bonuses and campaign credits collected across many accounts. It can be resold under the official rate because the input cost was zero. The catch is built in: the credit is finite, and the accounts holding it are the kind that platforms look for.
A shared account pool. One login, many users, requests spread across it. Cheap because the cost is divided. Fragile because the pool's owner — not you, not your code — decides when it ends.
A subscription converted into API calls. Someone's personal seat, resold by the call. Same fragility, one layer up.
None of these is automatically dishonest, and some run perfectly well for months. But they share one property that matters more than price:
The supply is not something the seller buys, so it is not something the seller can guarantee.
When the credits run out or the account is closed, the number on the pricing page turns out not to have been the important number. The remaining lifetime was.
The price test: below official is a countdown, not a discount
This one you can do in thirty seconds, with no insider knowledge.
Find the official price for the model you're using. Now look at what your provider charges. If it's meaningfully below that, the difference is being funded by something that isn't a margin — a promotion, someone else's account, or a subsidy with an end date.
Ask a direct question: where does the gap come from? A provider who buys officially at the official rate and marks it up can explain their number in one sentence. A provider who can't explain it usually can't sustain it either.
There's a second, quieter test. Watch the price over a month. Prices that only move in one direction — down, as they chase signups — and never move back up are being subsidised. Prices that move up when the upstream moves are just pass-through, which is what a reseller should be.
Migration cost: what you actually pay when you switch
The reason people stay with a dying provider is usually not loyalty, it's dread. So it's worth knowing exactly how much work a move is.
For an OpenAI-compatible endpoint it is normally three things:
- The base URL. Your provider's endpoint path — usually
/v1— changes. One string, in one config file or one environment variable. - The key. Swap the value; nothing else about your auth changes.
- Any tool config that hardcodes the old host — Cursor, Cline, Aider, an n8n HTTP node, a Claude Code wrapper. Each of those is one field.
If you use the Anthropic message format via an SDK or Claude Code, it's the same story with a /v1/messages path instead.
Set a calendar reminder and do a five-minute dry run while your current provider is still healthy. Point a single test script at a second provider, send one request, then switch it back. The point isn't to migrate. It's to find out that migrating takes five minutes — so that a 401 on a Saturday morning is an annoyance instead of an emergency.
A checklist you can run against your current provider
Five items. You can answer all of them from your own account, today, without asking the provider anything.
- Does the headline price sit below the model vendor's official rate? If yes, find out what funds the difference. "We buy at the official rate and charge a margin" is an answer. Silence is also an answer.
- Does my key work against two providers at once? Signing up elsewhere and sending one request costs you nothing and tells you whether you have a fallback or just a hope.
- Do I hold the account, or does someone hold it for me? If your key comes from a person who tops up their own account and passes you access, your balance sits with that person. Balance you don't control is not balance.
- Can I cancel or revoke my own key without asking anyone? If revocation requires a human in a chat group, the account isn't yours.
- Has this provider raised prices when the upstream did, or only when it needed signups? Pass-through pricing is a sign that real money is flowing. One-way pricing is usually a sign that it isn't.
NovaAPI · novaapi.lbase.com/blog/api-provider-disappeared.html · Five checks you can run against your current provider — today, from your own account.
One page, five questions.
If you can answer all five, you're in a much better position than most people reading this. If you can't answer item 3 or 4, that's the one to fix first.
What we do, and what we don't claim
This is where we run. Everything below is a description of how our supply works, not a promise about outcomes.
Stable. We call DeepSeek's official API directly (api.deepseek.com) on pay-as-you-go billing, with multi-path upstream routing and automatic failover, and no third-party proxy in between. We publish no availability percentage, because we haven't measured one.
Long-term. There is no expiry date on our upstream access. It isn't a trial, a limited batch, or a promotional grant that runs out. Our prices are published rather than quoted privately.
Safe — with one thing stated plainly. Your key is issued to you and revocable by you at any time, and your balance sits on your own account. We also screen every request through an automated moderation endpoint (OpenAI's omni-moderation-latest), and if a request is flagged we keep an excerpt of it for 180 days. Requests that aren't flagged aren't stored as content. "We don't log your prompts" is not true here, and we would rather you know that up front than discover it later. The practical consequence: don't send anything through any third-party API that you wouldn't send to a moderation service.
Not the same ban risk the cheap end of this market carries. The cheap providers run on harvested credits and pooled accounts, and when those get terminated, your access dies with them. We can't promise that DeepSeek will never do anything — but that failure mode isn't one our supply has, because we buy from DeepSeek's official API on a paid account of our own.
No temporary keys. One upstream vendor — DeepSeek's official API — rather than a rotating cast of borrowed or one-off keys, and no pool of shared accounts.
We are a reseller, not DeepSeek, and not an authorised partner. We hold no partnership and no reseller agreement. Our rate is DeepSeek's own off-peak rate × 2.5, published on our pricing page, and we are not the cheapest way to buy these tokens. If you can pay DeepSeek directly, that's cheaper and it's first-party — take it.
What we're selling isn't the lowest number. It's the base URL that's still working next month, and a checklist you can use on us as readily as on anyone else.