Before you sign
What we sell, how payment works, what we need to give you a price, and which agreements we will sign.
Read the 5 answersThe questions that come up in the week before a contract, answered without the sales padding. If yours is not here, the form at the bottom reaches a person.
Three sections, in the order the questions usually arrive.
What we sell, how payment works, what we need to give you a price, and which agreements we will sign.
Read the 5 answersWhat happens between signing and your first request, whether you have to change code, and running us alongside an account you already have.
Read the 3 answersHow fast we reply, where the authoritative status page lives, and what to include when you report a problem.
Read the 3 answersAccess to DeepSeek models under a commercial account we hold, delivered through an endpoint we issue to you. You get one contract, one invoice and one contact instead of opening and maintaining an account with the model provider yourself.
No. We are an independent provider. We are not affiliated with, endorsed by, or acting as an agent of DeepSeek. We buy access to their models and resell it under our own contract. If you need a direct relationship with the model provider, you should open one — and we will tell you so.
By bank transfer against a monthly invoice, in the name of your organization. There is no checkout on this site and we do not take card payments here. Your finance team gets a normal supplier invoice, not a receipt for a personal account.
Three things: roughly how much you expect to send each month, what you are running today, and when you need to be live. The first one drives the number; the other two tell us whether we can actually help. See how pricing works.
Yes to both. Send your templates and we will work through them. The data processing agreement page describes what ours covers so you can compare before you send anything.
We issue your key, run a test request that resembles your actual workload, and confirm which model identifier your key resolves to. Then we hand you the credentials and the name of the person who owns your account.
Usually the change is a base URL and a key. The request shape is compatible with the OpenAI SDK, so most teams point their existing client at our endpoint. Tokenization and edge cases in streaming are where differences show up — the migration note covers what to check.
Yes, and plenty of teams do — one path for experiments, ours for production traffic that needs an invoice. There is no exclusivity in the agreement.
Within one business day for anything, and faster for an active incident on your account. We will not quote you a support-hours matrix we have not staffed.
Not one of our own. The model service publishes its own status page, which is the authoritative place to look. The availability page explains why we cite it rather than mirror it.
The request you sent, the response you got back, roughly when it started, and whether it is every request or a fraction of them. That is usually enough to tell an upstream incident from something on your side in a single exchange.
The form at the bottom of this page reaches a person, not a queue. Tell us what you are building and what you need to know — if the answer is "we are not the right provider for this", we would rather say it early.
HELP · WHERE TO START
BEFORE YOU WRITE
Answers to the usual questions
billing, data, migration, limits
WHEN YOU WRITE
A person reads every message
usually within one business day
AFTER YOU SIGN
A named contact, not a queue
the same person who quoted you
Send us your monthly volume and what you use today. We usually reply within one business day with a price and a named contact.