Guia API

Início em 5 minutos

1. Registe-se e carregue

Registe-se ou entre e escolha montante e método de pagamento na carteira. As chamadas são liquidadas no saldo; o carregamento chega após confirmação.

2. Crie e guarde uma chave API

Crie uma chave e um limite mensal opcional. A chave completa aparece uma vez; guarde-a em segurança. Use uma por aplicação e não a exponha no navegador nem em repositórios públicos.

3. Escolha modelo e protocolo

Use um nome público do catálogo. OpenAI usa /v1; Anthropic usa /anthropic. Não substitua nomes públicos por identificadores internos do fornecedor.

4. Envie um pedido

Os SDK acrescentam o caminho ao Base URL; curl precisa do URL completo. Guarde chaves em variáveis do servidor e envie os cabeçalhos de autenticação. Use stream: true para streaming.

5. Consulte utilização e custos

Em Utilização, consulte custos por modelo ou chave, pedidos, estados e latência, e exporte CSV. A carteira liquida em CNY; consulte as unidades do catálogo.

Chaves API Catálogo de modelos

Os campos, nomes e caminhos do código são mantidos para desenvolvimento.

Referência técnica completa (inglês)

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.