Skip to main content
View on GitHub → Use AIsa as an OpenClaw model provider. Configure OpenClaw to access Qwen, DeepSeek, Kimi, GLM, and other models through one gateway.

Install

Start a new agent session after installing so the skill loads.

What can agents do with it?

OpenClaw setup

Configure OpenClaw with the AIsa provider.

Chinese LLM routing

Use Qwen, DeepSeek, GLM, and other Chinese models.

Global models

Route prompts to GPT, Claude, Gemini, and more.

Agent runtime defaults

Standardize model selection for OpenClaw workflows.

Quick Setup

Option 1: Environment Variable (fastest)

OpenClaw auto-detects AISA_API_KEY and registers AIsa as a provider. No config file changes needed.

Option 2: Interactive Onboarding

Option 3: CLI with Key

Option 4: Manual Config in ~/.openclaw/openclaw.json

OpenClaw uses each model’s cost fields only for its local spend estimates; AIsa bills from its own rates either way. The example leaves them at 0; copy current rates from aisa.one/models if you want OpenClaw’s estimates to be meaningful.

Available Models

Default Models (pre-configured, API-verified ✅)

Moonshot’s newest generation, aisa/kimi-k3, and its coding-oriented aisa/kimi-k2.7-code route are also available — they are not pre-configured above, so add them to your config manually if you want them.

⭐ Kimi K2.5 — Enterprise ZDR route

Kimi K2.5 is the Moonshot route covered by AIsa’s enterprise Zero Data Retention agreement. Key features:
  • Strong reasoning and multi-step problem solving
  • Competitive performance on coding and math benchmarks
  • Available through AIsa’s Moonshot partnership

🔒 Zero Data Retention (ZDR) — Enterprise-Grade Privacy

Accessing Kimi K2.5 through AIsa comes with enterprise-level Zero Data Retention guarantees. Users do not need to worry about data privacy — AIsa has executed a formal ZDR agreement with Moonshot AI. Under the Supplemental Enterprise Service Agreement (dated 10 February 2026) between AIsa and Kimi (Moonshot AI PTE. LTD.):
  • Customer data is NOT retained by Moonshot after processing
  • Generated outputs are NOT stored on Moonshot’s infrastructure
  • No data is used for model training — your prompts and completions remain private
  • Processing is governed by contractual enterprise terms, not consumer ToS
This makes AIsa the recommended path for privacy-sensitive or enterprise workloads that require access to Kimi K2.5. When calling Kimi K2.5 directly via Moonshot’s consumer API, standard consumer data policies apply — by routing through AIsa, your data benefits from the negotiated ZDR protections. ⚠️ Important: Temperature restriction Kimi K2.5 only accepts temperature=1.0. Using any other value will return an error:
If your OpenClaw config or agent sets a different temperature, override it for Kimi:
OpenClaw will use the model’s default temperature when not explicitly set.
Current AIsa rates for this route: https://aisa.one/models

Additional Models Available via AIsa

Users can add any model supported by AIsa to their config. The gateway serves 124 models as of September 30, 2026: Qwen family (24 models, including Wan image/video):
  • qwen3.8-max, qwen3.7-max, qwen3.7-max-2026-06-08, qwen3.7-plus, qwen3.7-flash, qwen3.7-flash-2026-07-15, qwen3-max, qwen-plus-2025-12-01, qwen-flash
  • qwen3-coder-plus, qwen3-coder-flash, qwen3-coder-480b-a35b-instruct
  • qwen3.6-plus, qwen3.6-plus-2026-04-02
  • qwen3-vl-plus, qwen3-vl-flash, qwen3-vl-flash-2025-10-15 (vision models)
  • qwen-mt-flash, qwen-mt-lite (translation models)
  • wan2.7-image, wan2.7-image-pro, wan2.7-t2v, wan2.7-i2v, wan2.7-r2v (media models)
DeepSeek (10 models):
  • deepseek-v4.1-flash, deepseek-v4-pro, deepseek-v4-pro-0813, deepseek-v4-flash, deepseek-v4-flash-0731, deepseek-v4-flash-vision-exp, deepseek-v3.2, deepseek-v3.1, deepseek-v3, deepseek-r1
Kimi / Moonshot (5 models):
  • kimi-k3, kimi-k2.7-code, kimi-k2.6, kimi-k2.5, kimi-k2-thinking
Also available: OpenAI GPT, image and embedding models (29), Claude series (13), xAI Grok (7), Zhipu GLM (6), ByteDance Seed/Seedream/Dreamina (10), MiniMax (4), Xiaomi MiMo (3), StepFun (3), HappyHorse video (3), Jina embeddings/reranker (3), Tencent Hunyuan (2), Gemini (1), and more. List all available models:

Model ID Versioning

AIsa uses versioned model IDs for some models. If you encounter a 503 - No available channels error, the model ID may need updating. Known model ID mappings: To check the latest available model IDs:

Switching Models

In chat (TUI):
Via CLI:

AIsa pricing for the default models

Current AIsa rates for these models are on aisa.one/models; see AI Model Pricing for how each model type is billed.

Official Partnerships

AIsa maintains verified partnerships with:
  • Alibaba Cloud — Qwen Key Account (full model family, 3 global regions: CN, US-Virginia, Singapore)
  • BytePlus — Doubao by ByteDance
  • DeepSeek — via Alibaba Cloud integration
  • Moonshot — Kimi integration (kimi-k3, kimi-k2.7-code, kimi-k2.6, kimi-k2.5, kimi-k2-thinking), with an enterprise Zero Data Retention (ZDR) agreement covering Kimi K2.5 (effective Feb 10, 2026)

Qwen Region Support

AIsa provides access to Qwen models across 3 global regions via Alibaba Cloud:
  • 🇨🇳 China (default)
  • 🇺🇸 US (Virginia)
  • 🇸🇬 Singapore
This comes from AIsa’s Key Account status with Alibaba Cloud.

Response Latency (tested Feb 2026)

Troubleshooting

”503 - No available channels” error

The model ID may be incorrect or outdated. Check the Model ID Versioning section above for correct IDs. Common fixes:
  • qwen3-plus -> use qwen-plus-2025-12-01
  • qwen3-flash -> use qwen-flash (or qwen-mt-flash for translation)

“Model not found” error

Ensure the model ID uses the aisa/ prefix in OpenClaw config:

Kimi K2.5 “invalid temperature” error

Kimi K2.5 only accepts temperature=1.0. If your config sets a different temperature, add a model-specific override or let OpenClaw use the default.

Kimi K2.5 empty response

In rare cases Kimi K2.5 may return empty content while consuming output tokens. Retry the request — this is typically transient.

API key not detected

  1. Check env var: echo $AISA_API_KEY
  2. Or verify in config: openclaw config get auth.profiles
  3. Re-run onboarding: openclaw onboard --auth-choice aisa-api-key

Streaming not working

AIsa uses the OpenAI-compatible API (openai-completions). Ensure your config has:

Rate limits or daily caps

AIsa has no daily request limits (unlike the free Qwen Portal which caps at 2,000 req/day).

Get an API Key

  1. Visit https://console.aisa.one/
  2. Sign up and create an API key
  3. Set it as AISA_API_KEY or use the onboarding wizard

Notes

  • AIsa’s endpoint is OpenAI-compatible (https://api.aisa.one/v1)
  • All models support streaming and function calling
  • supportsDeveloperRole is set to false for Qwen models
  • Context windows vary per model; see the model catalog rather than assuming a default
  • Reasoning (thinking) is enabled for all default models
  • Kimi K2.5 requires temperature=1.0 — other values cause API errors
  • Kimi K2.5 via AIsa is covered by enterprise Zero Data Retention (ZDR) — data is not retained or used for training
  • Image/Video generation models (WAN) are available but require separate configuration
  • AIsa API serves 124 models as of September 30, 2026 — use the models endpoint to discover the current list

Get started

  1. Sign up at aisa.one and create an API key in the console.
  2. Set it in your shell: export AISA_API_KEY="your-key".
  3. Install the skill with one of the commands under Install, then start a new agent session.

Quick Setup: How to Use AIsa in OpenClaw

Recommended OpenClaw setup path.

AIsa CN-LLM Route

Route Chinese-language prompts to Chinese LLMs.

AIsa LLM Router

Route prompts across supported models.