Skip to content
WALMINDWALMIND AI

Product line · Models

Cross-border AI API tokens, both directions

Overseas models reach teams in China, Chinese models reach teams abroad. One key, one interface, one usage bill.

Model access

Both directions · sample status

live

Overseas models · called from China

  • OpenAIGPT family
  • AnthropicClaude family
  • GoogleGemini family
  • xAIGrok family
  • MistralMistral family

Chinese models · called from abroad

  • DeepSeekDeepSeek family
  • QwenAlibaba Cloud
  • KimiMoonshot
  • ZhipuGLM family
  • DoubaoByteDance
  • MiniMaxMiniMax family

The model list in the console is authoritative. New models are added there first.

Routing

Two directions, one interface

The caller names a model. The gateway decides the route from the caller's origin and region.

In

Overseas models · called from China

Teams in China and outbound businesses call GPT, Claude, Gemini and others with a request body identical to the official API.

  • Same interface as the official SDKs, base_url changes
  • Keys issued per project, usage counted separately
Out

Chinese models · called from abroad

Overseas customers call DeepSeek, Qwen, Kimi and others, entering through the route nearest to the caller.

  • One account covers both directions
  • Caps and budgets per caller

Capabilities

What has to be managed after the key is issued

A common interface is the starting point. Usage, routing, logs and delivery decide whether it holds up over time.

01

One interface

OpenAI-compatible. Change base_url and key to move to another model, without touching application code.

02

Both directions

Overseas models into China and Chinese models out, sharing one account and one billing model.

03

Usage and budgets

Token usage by project, member and model, with monthly budgets and per-call caps.

04

Routes and retries

Multiple routes with fallback when one degrades. Timeouts and retry policy are configurable.

05

Logs and audit

Time, model, token count and caller recorded. Retention scope is set in the contract.

06

Delivery

Shared access works out of the box, or the gateway runs inside your own network.

Integration

Three steps to the first call

Existing OpenAI SDK code usually stays as it is.

  1. 01

    Get a key

    After signing or self-registration, issue a key per project in the console.

  2. 02

    Point base_url

    Set base_url to the gateway and pick a model id from the console list.

  3. 03

    Watch usage

    Token usage and cost by project, model and member.

curl
curl https://api.walmind.ai/v1/chat/completions \
  -H "Authorization: Bearer $WALMIND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "MODEL_ID",
    "messages": [{"role": "user", "content": "hello"}]
  }'

MODEL_ID comes from the console model list. For the OpenAI SDK, only base_url and api_key change.

Typical use

Four ways teams use it

Content for outbound markets

Copy, support replies and product descriptions generated per target language, with the model chosen for that language.

Model comparison

The same code path switched between models, comparing quality and cost on real traffic.

Chinese models for overseas customers

DeepSeek, Qwen and others reached from local networks, settled on one bill.

Primary and fallback models

When the primary model is unavailable, switch to the fallback by changing the model name.

Onboarding

Two ways to start

Companies sign a contract. Individuals and small teams can register and top up.

Enterprise contract

Qualification review, signed contract, bank transfer, monthly invoicing.

  • Per-token pricing, model rates in the contract annex
  • Invoices issued
  • Gateway can run on your premises

Self-registration

Register with an email, top up, generate a key, pay as you go.

  • Usable immediately, no review queue
  • Low-balance alerts
  • Upgrade to a contract later

FAQ

Questions about token access

Which models are available?

Overseas: OpenAI, Anthropic, Google, xAI, Mistral. Chinese: DeepSeek, Qwen, Kimi, Zhipu, Doubao, MiniMax. The console list is authoritative.

How much code has to change?

It is OpenAI-compatible. Change base_url and api_key; the request body stays the same.

Is prompt content stored?

Retention is set in the contract. It can be limited to time, model, token count and caller.

How is it billed?

Per token, with different rates per model. Budgets and per-call caps are set in the console.

Can we get invoices?

Contract customers are invoiced monthly.

Can the gateway run on our own network?

Yes. The gateway runs on your premises; model egress still goes through WALMIND routes.

Next step

Get one model working, then scale

Tell us the use case, the target model and the daily call volume. We reply with an integration plan and pricing.

Replies within one business day, 9:00–18:00 GMT+8.