Getting started

How you get access — and how little of it is your problem.

There is no self-service sign-up here, because the whole point is that a person handles the commercial side. Here is exactly what happens, in order.

Get a quote See how it works

What we need from you

Three things, and you probably have all of them already. We ask for them because we screen companies and end users against applicable export controls before onboarding — that step is not optional, and it is easier for you than discovering it later.

Your volume

Monthly tokens, and the shape of the workload. If you do not have the number, describe the job and we will estimate it.

  • Tokens / month
  • Workload shape

Your entity

Company name, country of registration, and where your end users are. This is what the compliance screen runs against.

  • Legal entity
  • Country
  • End-user regions

Who signs

Whoever can commit the company. We will send the agreement to them directly and work through any amendments their legal team wants.

  • Signatory
  • Billing contact
  • Technical contact

What happens, in order

DAY 0

You send the form

Two minutes. Volume, entity, and who to talk to. A person reads it — there is no autoresponder loop.

DAY 1

We reply with a rate

Usually within one business day, from a named contact. If we cannot beat your current cost, we say so and stop there.

DAYS 2–5

Contract and compliance

We send the agreement, answer your legal team's questions, sign a DPA if you need one, and run the compliance screen.

THEN

Keys and one line of code

You get your key and endpoint. Change base_url and the key. Keep your current provider configured as a fallback.

What changes in your code

One line, in most codebases. The API is OpenAI-compatible, so the official SDKs work unchanged. If your integration is more involved than that, tell us — we would rather find out before you sign than after.

Questions people ask at this stage

How long does onboarding actually take?

Usually a few days, and the long pole is almost always the contract rather than anything technical. If your legal team has no amendments, it is faster.

Can we trial it before signing?

Yes. We can give you a limited key to run a real workload through, so you are testing on your own data rather than a demo. Ask for it in the form.

Do we need to change our SDK?

No. The endpoints follow the OpenAI chat-completions schema, so the official SDKs work as-is. In most codebases the change is base_url plus the key.

How many DeepSeek API keys can we have?

If your policy needs separate keys per environment, per team, or on a rotation schedule, put that in the form and we will confirm what is possible before you sign rather than after. It is the kind of requirement that is easy to arrange at onboarding and awkward to retrofit later.

What if we already have a DeepSeek account?

Then you are well placed to compare. Run a share of traffic through us and keep the direct account configured as a fallback — you can move it back the same way.

WE HANDLEYOU DO

Diagram of the flow: three stages connected by arrows, with the middle stage highlighted.

  1. 1

    Tell us your volume

    Monthly token usage, and what you are running today. If we cannot beat your current cost, we say so.

    • Quote
    • Contract
    • Invoice

  2. 2

    We quote and contract

    A named account contact, a negotiable agreement, an invoice.

    - base_url="…"
+ base_url="…"
# nothing else changes

  3. 3

    You change one line

    Point your existing client at our endpoint. Keep a fallback.

Steps one and two are ours. Only step three lands on your side of the line.Diagram of the onboarding sequence. Not a screenshot.

Tell us what you're running.

Send us your monthly volume and what you use today. We usually reply within one business day with a price and a named contact.

Get a quote See how it works