DeepSeek API usage is billed per token, which means an account without balance cannot make requests. Teams in China usually run into the same set of questions: which top-up route to use, how currency conversion and fees apply, how to get an invoice, and how to manage quota across a team.

This guide walks through both top-up paths, the details worth confirming before you pay, and the settings that keep spending predictable after the credit arrives.

Note: DeepSeek is a trademark of its owner. This article reflects common practices as of October 2026. Refer to the official platform or the in-site documentation for current rules.

1. Two Top-Up Paths

Official DeepSeek

You top up inside the DeepSeek open platform and bind a payment method. This route fits teams that can use the official platform directly and need official billing records for reimbursement.

ZSQH AI Gateway

  1. Register for the ZSQH AI Gateway.
  2. Open the wallet or top-up page.
  3. Select an amount and a payment method.
  4. After the credit arrives, create an API key and start calling.

This route fits teams that need domestic payment options, one bill across several models, and the freedom to switch models without opening a separate account with every provider.

2. What to Confirm Before Topping Up

Item What to confirm
Currency CNY or USD, and whether any conversion applies
Arrival Instant or delayed, and how a failed payment is refunded
Minimum amount Whether a minimum top-up is required
Invoice Whether one can be issued, which type, and on what schedule
Refund Whether unused balance can be returned
Validity Whether the balance expires

Ask for these details in writing before a large payment. A low headline price can hide conversion spreads or processing fees, and invoice terms often differ between individual top-ups and enterprise contracts. For team use, also confirm whether the credit is shared across API keys or allocated per key, because that decision affects how you set quotas later.

3. Calling the API After Top-Up

export DEEPSEEK_API_KEY="sk-your-key"

curl "https://ai.zhongshangqihang.com/v1/chat/completions" \
  -H "Authorization: Bearer $DEEPSEEK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"deepseek-chat","messages":[{"role":"user","content":"Reply with OK only"}]}'

Model names follow the model pricing page. Send a small request first to confirm that the key, the Base URL, and the balance are all working before you connect the endpoint to production code. If you plan to use several models, test each model name separately; a key can be valid while a particular model is not enabled for your account.

4. Cost Control

  1. Issue one key per person and set a quota for each project.
  2. Use a cheaper model for simple tasks such as classification or short replies.
  3. Summarize or split long documents before sending them.
  4. Monitor retries and HTTP 429 responses, which often signal limit problems rather than real demand.
  5. Review usage logs every week.
  6. Set daily and monthly budgets.

Token billing is easy to understand but hard to predict when prompts grow. A single long context window can cost more than many short requests, and automatic retries can quietly multiply the bill. Watch the distribution of input and output tokens, not just the total request count. If one feature dominates usage, consider caching, shorter prompts, or a smaller model for that feature.

5. Invoices and Compliance

For enterprise purchasing, confirm the following:

  • Invoice type (general or special VAT invoice).
  • Contract or order documentation.
  • Payment receipt.
  • Data usage terms.

Individual developers testing the API should start with a small top-up to avoid leaving idle balance. If procurement requires a contract, begin that process before you need production capacity; paperwork often takes longer than the technical integration.

6. FAQ

Why does the API still report insufficient balance after a top-up?

Possible causes include a delayed credit, a per-key quota limit, a model that has not been enabled, or a request sent to a more expensive model than expected. Check the console balance and the request logs before paying again.

Does the balance expire?

It depends on the platform rules. Confirm the validity period at the time of top-up and record it somewhere your team can see.

Can I get a refund?

It depends on the terms. Unused credit, promotional credit, and already consumed usage may follow different rules, so clarify this before a large payment.

Which is more cost-effective: official top-up or gateway top-up?

Compare the full picture: exchange rate, processing fees, invoices, access stability, and operational overhead. A slightly higher unit price can still be the better choice if it removes payment friction and support work.

7. Security Reminders

  • Never enter your key on a page that is not the official site.
  • Verify the domain and the recipient before paying.
  • Keep order numbers and receipts.
  • Do not trust "cheap top-up" offers that ask for your account password.
  • For companies, use corporate payment and contract processes.

Next Steps

If you need domestic top-up, a unified bill, or multi-model access, you can register for the ZSQH AI Gateway and start with a small top-up to validate the flow. Model names and prices are listed on the model pricing page.

Related reading: