DeepSeek API from the United States

Run a DeepSeek request from the US without rebuilding your client.

Use a USD-funded AIWave account and an OpenAI-compatible client to test a DeepSeek route from the United States. Keep the dated rate and request record visible.

Run your first request Check dated pricing

Start with a request you can verify.

Keep the model ID, status, usage fields, and effective group beside the test result.

One request before production traffic

PAYMENTCHECK

Fund one USD account.

Use the payment method shown in Console, then verify the credited balance before sending a production request.

CLIENTCHECK

Keep the OpenAI request shape.

Change the base URL and key, pin a tested model ID, and leave timeout and retry rules under application control.

EVIDENCECHECK

Read the completed request record.

Check input, cache-hit input, output, effective group, status, timestamp, and charge after the call.

curlOpenAI-compatible chat request

curl https://aiwave.live/v1/chat/completions \
  -H "Authorization: Bearer $AIWAVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"deepseek-v4-pro","messages":[{"role":"user","content":"Reply with one sentence."}]}'

Questions to settle before you send traffic.

The answers keep account, route, and billing boundaries explicit.

Do I need a Chinese phone number?

AIWave account requirements are shown in the current sign-up flow. A DeepSeek route can be tested through the AIWave API without opening a separate provider account.

Does the request use an OpenAI-compatible endpoint?

Supported chat requests use the AIWave /v1/chat/completions route. Test your exact request fields before migrating traffic.

Where do I verify the price?

Use the dated public rate card and confirm the effective account group in Console before funding a production workload.