Use AIsa in OpenClaw

OpenClaw has a built-in MCP client. Add AIsa as a remote MCP server, sign in once, and your OpenClaw agents can discover and call AIsa capabilities across web research, finance, social, SEO, sales, and more. AIsa MCP server:

https://mcp.aisa.one/mcp

This guide has two parts:

Add the AIsa MCP server so OpenClaw can use AIsa’s data and tools.
Optionally, configure AIsa as OpenClaw’s LLM provider.

1. Connect AIsa capabilities

Step 1: Add the server

openclaw mcp add aisa --url https://mcp.aisa.one/mcp --transport streamable-http --timeout 30 --auth oauth

Keep --transport streamable-http and --timeout 30. Without --transport, OpenClaw connects over SSE and the server rejects it with 405. Without --timeout, the connection test can time out.

openclaw mcp login aisa

OpenClaw prints an authorization URL. Open it, sign in to AIsa, and approve access. The browser is then redirected to a local callback URL (http://127.0.0.1:8989/oauth/callback?code=...); the page may not load. Copy the code value from the address bar and finish the sign-in:

openclaw mcp login aisa --code <code>

Use your API key instead of OAuth

For headless hosts, pass the API key as a Bearer header instead of --auth oauth. The single quotes keep ${AISA_API_KEY} unexpanded, so OpenClaw stores the reference and reads the key from the environment at runtime instead of saving it in openclaw.json:

export AISA_API_KEY="sk-aisa-..."
openclaw mcp add aisa --url https://mcp.aisa.one/mcp --transport streamable-http --timeout 30 \
  --header 'Authorization=Bearer ${AISA_API_KEY}'

AISA_API_KEY must be set in the environment that runs OpenClaw, or in the env block of openclaw.json.

Step 3: Verify and reload

openclaw mcp probe

The output should include aisa: 7 tools. Restart the gateway so running agents pick up the server:

openclaw gateway restart

OpenClaw now has the AIsa tools. search, list_categories, get_details, batch_get_schema, and batch_quote (prices exact calls without running them) are free; use and batch_use run calls and are billed per call. Try:

Use AIsa capabilities to search the web and summarize the latest information about OpenClaw.

2. Optional: use AIsa as the LLM provider

OpenClaw can also route its agents’ LLM requests through AIsa. Edit openclaw.json directly for full control over the model configuration: custom model lists, fallback chains, credentials in OpenClaw’s auth store, or per-channel routing.

Step 1: Get your AIsa API key

console.aisa.one

Navigate to API Keys

console.aisa.one/api-keys

Create a new key

Give it a label like openclaw-local. Copy the value (starts with sk-aisa-) immediately — it is shown only once.

Step 2: Set your API key

Add the key to ~/.openclaw/openclaw.json or export it in your shell:

export AISA_API_KEY="sk-aisa-..."

Prefer an environment variable over hardcoding the key in openclaw.json. See Authentication for rotation and storage best practices.

Step 3: Configure the AIsa provider

Add this block to your ~/.openclaw/openclaw.json:

{
  "env": {
    "AISA_API_KEY": "sk-aisa-..."
  },
  "models": {
    "mode": "merge",
    "providers": {
      "aisa": {
        "baseUrl": "https://api.aisa.one/v1",
        "apiKey": "${AISA_API_KEY}",
        "api": "openai-completions",
        "models": [
          { "id": "gpt-5.4-mini", "name": "GPT-5.4 Mini" },
          { "id": "kimi-k2.5", "name": "Kimi K2.5" },
          { "id": "claude-opus-4-8", "name": "Claude Opus 4.8" },
          { "id": "gemini-3.8-flash", "name": "Gemini 3.8 Flash" },
          { "id": "deepseek-v4.1-flash", "name": "DeepSeek V4.1 Flash" },
          { "id": "qwen3.7-max", "name": "Qwen3.7 Max" },
          { "id": "MiniMax-M3", "name": "MiniMax M3" },
          { "id": "glm-5", "name": "GLM 5" }
        ]
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "aisa/kimi-k2.5"
      },
      "models": {
        "aisa/kimi-k2.5": {}
      }
    }
  }
}

OpenClaw now recognizes the aisa provider. Reference any model using the aisa/<model-id> format.

Step 4: Restart OpenClaw

openclaw gateway restart

Your agents will now route requests through AIsa.

Video walkthrough

LLM model format

Always use the aisa/<model-id> format — for example, aisa/kimi-k2.5, aisa/gpt-5.4, or aisa/claude-opus-4-8. Add any supported model to the models array in your provider config; see the full list in the model catalog.

Advanced configuration

Fallback chains

If the primary model fails (due to an upstream outage or rate limit), OpenClaw can automatically retry with a fallback model:

{
  "agents": {
    "defaults": {
      "model": {
        "primary": "aisa/kimi-k2.5",
        "fallbacks": ["aisa/gpt-5.4-mini"]
      },
      "models": {
        "aisa/kimi-k2.5": {},
        "aisa/gpt-5.4-mini": {}
      }
    }
  }
}

Store the key in OpenClaw’s auth store

Keep your API key out of openclaw.json by saving it in OpenClaw’s local auth store:

printf "%s\n" "$AISA_API_KEY" | openclaw models auth paste-api-key --provider aisa

The key is saved under the aisa:manual profile (pass --profile-id to name it differently). OpenClaw resolves the credential from the auth store, so you can remove apiKey from models.providers.aisa.

Per-channel models

Run a different model in specific chats. Keys under channels.modelByChannel.<platform> are channel or group IDs on that platform; values are aisa/<model-id>:

{
  "channels": {
    "modelByChannel": {
      "telegram": {
        "-1001234567890": "aisa/kimi-k2.5"
      },
      "discord": {
        "123456789012345678": "aisa/claude-opus-4-8"
      }
    }
  }
}

OpenClaw validates openclaw.json strictly: unknown top-level keys such as telegram or discord make the Gateway refuse to start.

Monitoring usage

Track your usage and per-request details in the AIsa dashboard. See Usage Logs for available metrics and logs.

Troubleshooting

'No API key found for provider aisa'

Fix:

Confirm AISA_API_KEY is set: echo $AISA_API_KEY
Verify openclaw.json references ${AISA_API_KEY} (not a literal string).
Restart OpenClaw so it re-reads environment variables.
As a last resort, hardcode the key to confirm the rest of the config works, then move it back to an environment variable.

Authentication errors (401 / 403)

Fix:

Confirm the key is valid in the dashboard.
Ensure baseUrl is exactly https://api.aisa.one/v1 (with no trailing slash).
See Authentication for rotation guidance.

Model not working

Fix:

Double-check the model ID against the catalog.
Make sure the model is listed in models.providers.aisa.models.
Reference it as aisa/<model-id>.

AIsa tools missing

Fix:

Run openclaw mcp list and confirm aisa is configured with streamable-http.
Run openclaw mcp status --verbose to check the sign-in; if needed, run openclaw mcp login aisa again.
Run openclaw gateway restart so running agents reload the server.

'SSE error: Non-200 status code (405)' or 'Request timed out'

Fix: openclaw mcp add tests the connection before saving, so a failed add saves nothing. Run it again with --transport streamable-http --timeout 30. To replace an existing entry, run openclaw mcp unset aisa first.

'Blocked: resolves to private/internal/special-use IP address'

Fix: OpenClaw blocks hosts that resolve to private or special-use addresses. A proxy in fake-IP mode (for example Clash or Surge) can make clerk.aisa.one resolve this way. Exclude aisa.one from fake-IP, or use the API key option instead of OAuth.

Authentication

API key lifecycle, storage, and best practices.

Model Catalog

Current model IDs, context windows, endpoints, capabilities, and billing notes.

OpenClaw docs

Official OpenClaw documentation.

Coding Agents

Agent Platforms

Build Your Own

Use AIsa in OpenClaw

1. Connect AIsa capabilities

Step 1: Add the server

Step 3: Verify and reload

2. Optional: use AIsa as the LLM provider

Step 1: Get your AIsa API key

Step 2: Set your API key

Step 3: Configure the AIsa provider

Step 4: Restart OpenClaw

Video walkthrough

LLM model format

Advanced configuration

Fallback chains

Store the key in OpenClaw’s auth store

Per-channel models

Monitoring usage

Troubleshooting

Authentication

Model Catalog

OpenClaw docs

​1. Connect AIsa capabilities

​Step 1: Add the server

​Step 2: Sign in

​Step 3: Verify and reload

​2. Optional: use AIsa as the LLM provider

​Step 1: Get your AIsa API key

​Step 2: Set your API key

​Step 3: Configure the AIsa provider

​Step 4: Restart OpenClaw

​Video walkthrough

​LLM model format

​Advanced configuration

​Fallback chains

​Store the key in OpenClaw’s auth store

​Per-channel models

​Monitoring usage

​Troubleshooting

​Related

Authentication

Model Catalog

OpenClaw docs

1. Connect AIsa capabilities

Step 1: Add the server

Step 2: Sign in

Step 3: Verify and reload

2. Optional: use AIsa as the LLM provider

Step 1: Get your AIsa API key

Step 2: Set your API key

Step 3: Configure the AIsa provider

Step 4: Restart OpenClaw

Video walkthrough

LLM model format

Advanced configuration

Fallback chains

Store the key in OpenClaw’s auth store

Per-channel models

Monitoring usage

Troubleshooting

Related