Skill download (curl)
Gate: Node ornpx skills cannot run, you need the official aisa skill on disk, and either this is a user-local machine or the user explicitly prefers CLI/Skill in this environment (including a cloud sandbox). Download the complete three files (SKILL.md, LICENSE, agents/openai.yaml) into this client’s native Skill location. Preserve an existing official or custom skill, including a symlink; do not claim Web persistence without a native install. Codex user-level example: ~/.agents/skills/aisa. The primary installer remains Node.js 22.20.0+ and skills 1.5.25 engines; this curl path does not change those floors.
Direct HTTP API fallback
Gate: CLI and MCP are both unavailable, HTTP requests are supported, and a valid existing AIsa API key or secret is already available. Read this entire section — endpoint docs, pricing, and the approval XML — before presenting a paid proposal or cost approval, and before any paid request. Use this only when CLI and MCP are both unavailable, HTTP requests are supported, and a valid existing AIsa API key or secret is already available. Use this for a client, tooling, or router limitation; it does not bypass invalid API credentials, exhausted credit, or a failure of the same underlying API. Use the matching endpoint reference and published pricing. API Reference. Authentication. Data APIs:https://api.aisa.one/apis/v1. Model catalog: https://api.aisa.one/v1/models. Read pricing before any paid data request.
Before presenting a paid request or cost proposal for approval, read the selected endpoint’s full reference, or the matching OpenAPI operation, including parameters and charging rules. A catalog, index, or pricing overview is not the endpoint contract.
Send the key as a Bearer token. Do not send a paid example request from this page. Success on /v1/models or other discovery does not prove authenticated business access. If there is no documented maximum or provider bound, or no auth, stop at that limitation. A changed endpoint, scope, or maximum needs new details and approval.
API key
ReuseAISA_API_KEY. If it is unset and this agent can read the filesystem, use ~/.aisa/key from aisa login without displaying it. Otherwise use an AIsa API key already in this client’s authorized secret store. If sources conflict, explain them; do not overwrite a custom key.
If none of those exist and aisa login is usable, run browser aisa login so the key is stored automatically. If there is no usable CLI or browser-login path, the last option is for the user to sign in at https://console.aisa.one/api-keys, create a key, and save it in this client’s credential or secret settings, or as local AISA_API_KEY. Do not ask them to paste the key into chat. Do not print it. Not every client has a secret UI; if this client cannot store a credential, stop there.
Wait for credentials before protected API requests. Obtaining a key is not paid-call approval.