Bundle Pluginstructural

AIsa Provider

OpenClaw native provider plugin for the AIsa unified Chinese model gateway

@aisa/openclaw-aisa-provider · runtime id @aisa/openclaw-aisa-provider
Install
openclaw bundles install clawhub:@aisa/openclaw-aisa-provider
Latest Release
Version 0.1.0
Compatibility
{
  "builtWithOpenClawVersion": "2026.3.28",
  "pluginApiRange": "0.1.0"
}
Capabilities
{
  "bundleFormat": "generic",
  "capabilityTags": [
    "bundle-only",
    "format:generic",
    "host:openclaw"
  ],
  "executesCode": false,
  "hostTargets": [
    "openclaw"
  ],
  "runtimeId": "@aisa/openclaw-aisa-provider"
}
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The package registers an 'aisa' provider, exposes an OpenAI-compatible gateway, lists AIsa model refs, and asks for an AISA_API_KEY — all consistent with a provider plugin for the AIsa gateway.
Instruction Scope
SKILL.md and code only instruct installation of the plugin, restarting the gateway, and providing an AISA_API_KEY (or using onboarding). The runtime code registers provider metadata and catalog entries; it does not read unrelated files, access other credentials, or direct data to unexpected endpoints.
Install Mechanism
No install spec or external downloads are present. The package is source-only (TypeScript files and manifest) and relies on the OpenClaw plugin SDK — nothing writes or downloads arbitrary code from untrusted URLs.
Credentials
The plugin reasonably requires a single provider API key (AISA_API_KEY). One minor inconsistency: the top-level registry metadata in the submission listed 'Required env vars: none' while the plugin and SKILL.md clearly reference AISA_API_KEY; this appears to be a metadata omission rather than malicious behavior.
Persistence & Privilege
The plugin does not request 'always: true' or other elevated persistent privileges. It registers itself as a normal provider and uses OpenClaw onboarding hooks only for its own config.
Assessment
This package appears internally consistent for adding an AIsa provider: it only needs your AISA_API_KEY and registers model metadata and onboarding hooks. Before installing, confirm you trust the AIsa endpoint (https://api.aisa.one) and that the API key's permissions are appropriate. Note the registry metadata in the submission omitted the required env var — verify the listed source/origin (author or ClawHub listing) if you need provenance assurance. Rotate or scope the API key if possible and review the small code bundle (it’s brief and readable) if you want additional confidence.
Verification
{
  "scanStatus": "pending",
  "scope": "artifact-only",
  "summary": "Validated package structure and extracted metadata.",
  "tier": "structural"
}
Tags
{
  "latest": "0.1.0"
}

AIsa Provider Plugin for OpenClaw

This package converts the AIsa provider pull request into a native OpenClaw code plugin that can be published to ClawHub as a Code Plugin.

What this plugin does

The plugin registers a provider named aisa and exposes a unified OpenAI-compatible gateway for major Chinese models through:

  • AISA_API_KEY
  • https://api.aisa.one/v1
  • default model aisa/kimi-k2.5

The bundled catalog currently includes:

Model RefNameInputReasoningContext
aisa/minimax-m2.1MiniMax M2.1textNo200k
aisa/kimi-k2.5Kimi K2.5textYes256k
aisa/qwen3-maxQwen3 Maxtext, imageYes256k
aisa/glm-5GLM-5text, imageYes200k
aisa/deepseek-v3.2DeepSeek V3.2textYes128k
aisa/seed-1-8-251228Seed 1.8textYes128k

Directory layout

openclaw-aisa-provider/
├── package.json
├── openclaw.plugin.json
├── index.ts
├── README.md
└── src/
    ├── constants.ts
    ├── onboard.ts
    └── provider-catalog.ts

Local installation

openclaw plugins install ./openclaw-aisa-provider
openclaw gateway restart

Then configure credentials either by environment variable:

export AISA_API_KEY="your-key"

or through onboarding:

openclaw onboard --auth-choice aisa-api-key

Publish to ClawHub

On ClawHub, upload this folder as a Code Plugin. The platform will inspect the package, detect openclaw.plugin.json, and prefill package metadata.

Notes

This package intentionally extracts the provider behavior from the PR into plugin space. It does not yet include the follow-up reliability fixes mentioned in the PR, such as JSON fence stripping, stricter structured-output prompting, or automatic retry logic. Those should be added either as provider runtime wrappers or as separate companion plugins.