Stock & Crypto Analysis — AIsa Edition

AIsa agent rules (shared)

These rules apply to every AIsa-backed skill and are copied from https://aisa.one/llms.txt, the single authoritative agent rule source. When this block and the rest of this skill disagree, follow this block.

Connect (MCP first)

Pick the first option that applies. Run the command yourself; the user only approves the browser sign-in.

• A. Your client supports remote MCP and can open a browser (default). Add a remote MCP server named AIsa with URL https://mcp.aisa.one/mcp (Streamable HTTP), using your client's own command or config file. Auth: browser OAuth, no key needed. In a chat app (Claude, ChatGPT), the user adds it as a custom connector in settings. Adding the server does not always start sign-in. If no sign-in window opens, start it from the client's own MCP authentication entry (a menu, command, or connector button); if only the user can reach that entry, tell them where it is. Sign-in is the slow step, not the API. Before it starts, tell the user in one line that an AIsa sign-in window or card is about to open and to click Allow (one click if the browser is already signed in to AIsa). Do not call step 2 until the user says sign-in is done or the AIsa tools appear; calling it earlier only returns 401, so do not retry in a loop. If the client must restart to load the server, tell the user and wait. If you cannot add the connector yourself (sandbox, permission denied), give the user the server name and URL above and wait. Do not fall back to another method.
• B. Your client supports remote MCP but has no browser (CI, SSH, container). Same endpoint, with the header Authorization: Bearer $AISA_API_KEY set in your client's MCP config instead of browser sign-in. If AISA_API_KEY is not set, ask the user to create a key at https://console.aisa.one/api-keys and set it in the environment; never ask them to paste it into chat. Never print, log, or commit the key.
• C. The client has no MCP support. Use the CLI: npm install -g @aisa-one/cli && aisa login (Node.js 18+). Guide: https://aisa.one/docs/get-started/cli.md
• D. Calling AIsa over HTTP from your own code. LLMs, OpenAI-compatible: https://api.aisa.one/v1 (Gemini GenerateContent: https://api.aisa.one/v1beta). Data APIs: https://api.aisa.one/apis/v1. Auth: Authorization: Bearer $AISA_API_KEY. Exact paths and schemas: https://aisa.one/docs/api-reference

Direct HTTP (D) is a gated fallback, not the default. Gate (https://aisa.one/docs/get-started/cli.md#direct-http-fallback): "CLI and MCP are both unavailable, HTTP requests are supported, and a valid existing AIsa API key is already available." The curl and script examples in this skill exist for that fallback; when a connection exists, run the same operation through MCP (search → batch_get_schema → batch_quote → batch_use) or the CLI (aisa search → aisa schema → aisa quote → aisa call). Take tool names and arguments from search or batch_get_schema. Never invent them.