Dux API

Initium quinque minutorum

1. Nomen da et pecuniam adde

Nomen da vel ingredere, deinde summam et modum solvendi elige. Invocationes e crumena solvuntur; pecunia post confirmationem accedit.

2. Clavem API crea et serva

Clavem in tabula crea et limitem menstruum statuere potes. Clavis semel ostenditur; tute serva. Singulis applicationibus claves proprias da, nec in codice publico divulga.

3. Exemplar et protocollum elige

Nomine publico e catalogo utere. Clientes OpenAI /v1, Anthropic /anthropic adhibent. ID interna nomina publica non substituant.

4. Petitionem mitte

SDK itinera URL basi addunt; curl URL integrum requirit. Claves in variabilibus ministri serva et capita authenticationis mitte. Ad fluxum stream: true adhibe.

5. Usum et sumptus observa

Sumptus per exemplar vel clavem, petitiones, status et moras vide, atque CSV excipe. Crumena in CNY solvitur; unitates catalogi sequere.

Claves API Catalogus modelorum

Nomina camporum, exemplaria et itinera in codice immutata manent.

Referentia technica integra (Anglice)

Getting started

5-minute quickstart

Five steps from a fresh account to a working LLM call. If you already have a key, jump straight to Use your API key.

Step 1 — Create an account

Go to Sign up.
Enter your email + a password. We send an activation link — click it to switch the account from PENDING_VERIFICATION to ACTIVE.
You land on the developer console.

Already activated? Sign in at /sign-in.

Step 2 — Add funds

Every relay call settles against your wallet, so it starts at zero balance and you need to top up before it works.

Open Billing.
Pick an amount and a payment method (Alipay if configured, or the mock provider in dev environments).
The wallet credit lands when the payment callback fires (seconds for Alipay, instant for mock).

Charges are denominated in CN¥ minor (分). Each model alias has a published per-1k-token price — see Models.

Step 3 — Create an API key

Open API keys.
Pick a name (e.g. local-dev) and an optional monthly spend cap.
Click Create API key. The reveal banner shows the token starting with tsk_. Copy it now — the platform never displays the full token again.

Step 4 — Send a request

Two URL forms come up depending on the client you use:

Base URL (the value you pass to an SDK's baseURL / base_url field): https://chinzy.com/v1
Full endpoint URL (the URL you put in raw HTTP / curl): https://chinzy.com/v1/chat/completions

SDKs (OpenAI, Anthropic, etc.) only need the base URL — they append /chat/completions themselves. Curl needs the full path because it has no concept of a base URL. Quick smoke test with curl:

curl https://chinzy.com/v1/chat/completions \
  -H "Authorization: Bearer tsk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.2",
    "messages": [{"role": "user", "content": "Say hi in one sentence"}]
  }'

Expected response shape: a JSON body with choices[0].message.content populated and a usage block. Status 200.

Got a different status code? Skip to the error table.

Step 5 — Watch your spend

Open Usage. Within seconds your first call shows up:

Cycle spend — total charged this calendar month.
By model / By API key — breakdowns sorted by spend.
Recent calls — last 50 requests with status, latency, and cost. The status code links to the request log row in the operator console for debugging if needed.
Download CSV — pull 7 / 30 / 90 days of activity into a spreadsheet for accounting.

You're live

From here, common next steps:

Switch your existing OpenAI / Anthropic SDK code to point at our base URL — see SDK examples.
Browse the full Models catalog for aliases and pricing.
Set monthly caps on each key so a runaway client can't drain the wallet.