@aisa-one/cli 0.2.2 → 0.2.4

package/CHANGELOG.md

@@ -7,6 +7,157 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.4] — 2026-08-07
+
+Text-only follow-up to 0.2.3: no behavioural change, but the URL it printed
+sent people to a 404.
+
+### Fixed
+
+- **`aisa usage` and `aisa login` pointed at `aisa.one/dashboard`, which
+  returns 404.** The customer console is served at `console.aisa.one`; the
+  API-key and usage-log pages are `/api-keys` and `/logs`. Both commands and
+  both README references now say so.
+
+### Changed
+
+- **The brand is written `AIsa`, not `AISA`,** in `--help` output, the npm
+  package description, the skill templates, and the README. The `AISA_*`
+  environment variables and `X-AISA-*` response headers are technical
+  identifiers and keep their existing casing.
+
+## [0.2.3] — 2026-08-07
+
+Every command documented in the README was checked against the live gateway.
+Eight were broken. This release fixes everything that the gateway already
+supports today; nothing here depends on a backend change.
+
+### Added
+
+- **`aisa run --show-cost`** prints the gateway's billing headers
+  (`X-AISA-Price-USD`, accounted/estimated credits, credit model, pricing
+  strategy, price key, request id) on stderr, leaving `--raw | jq` a clean
+  pipe. Metered providers are the reason it exists: DataForSEO and Jina bill
+  per consumed credit, but `/info/apis` reports every provider's pricing as
+  flat `per_request`, so the headers are the only accurate record of what a
+  call cost. Routes that report no amount say so explicitly rather than
+  printing nothing, which would read as "this was free".
+
+- **Shell completion.** `aisa completion <bash|zsh|fish>` prints an installable
+  script; with no argument it detects the shell from `$SHELL`. Beyond commands
+  and flags it completes provider slugs, a provider's endpoints, skill names,
+  and model ids from the local cache. Completion never makes a network request —
+  a cold cache simply offers no dynamic values rather than stalling the prompt.
+- **`aisa api list` / `show` / `search` / `code` now work.** They read the
+  public `/info/apis` catalog — 29 providers, 950+ endpoints — and **no longer
+  require an API key**, so the catalog is browsable before signup. Note that a
+  provider's id is not always its URL slug (`brave-search` serves
+  `/apis/v1/brave/...`); `api show` prints the runnable path.
+- **`aisa cache clear` / `cache path`** for the on-disk catalog and skills
+  cache (`~/.aisa/cache`, overridable with `AISA_CACHE_DIR`). Most commands
+  accept `--refresh` to bypass it.
+- **`aisa run --llm` / `--domain`** to override base-URL detection.
+- **`aisa video create` now builds the right request body per model family.**
+  The gateway rewrites only the top-level `model` and forwards the rest, so the
+  body belongs to the owning vendor: Seedance needs a `content` array and
+  rejects the Bailian `input`/`parameters` shape with a 400, while i2v and r2v
+  models need `input.media[]`. New `--image` (shorthand for
+  `--media first_frame=<url>`), `--media <type=url>` covering `first_frame`,
+  `last_frame`, `driving_audio` and `first_clip`, and `--body '<json>'` as a
+  verbatim escape hatch. A model that needs source media now fails immediately
+  instead of being accepted, billed, and failing upstream a minute later.
+- **`aisa video create --resolution` / `--duration`**, and `--output` now
+  actually downloads the finished clip (it was previously accepted and ignored).
+- **`aisa screener --min-market-cap` and `--filter field:op:value`**; sector
+  names are normalised to GICS, so `--sector Technology` resolves to
+  `Information Technology` rather than silently matching nothing.
+- **`aisa crypto --id` and `--source`**; `aisa skills install --force`;
+  `aisa skills list --category` / `--limit` (previously accepted and ignored).
+- `GITHUB_TOKEN` / `GH_TOKEN` is used for skills-registry requests when set,
+  raising the GitHub rate limit from 60/hr to 5000/hr.
+
+### Fixed
+
+- **`aisa run` reached only 6 of 29 providers.** The slug whitelist listed nine
+  entries, two of which (`services`, `crypto`) do not exist, and everything
+  outside it was sent to the LLM gateway and 404'd. Detection is inverted: the
+  whitelist now covers LLM gateway routes, which are hardcoded server-side, and
+  everything else defaults to the integration base — so newly added providers
+  work without a CLI release. A 404 now suggests near-miss slugs.
+- **`aisa run classify ...` reached the wrong base.** The gateway serves
+  `POST /v1/classify` (Jina classification), but it was missing from the LLM
+  route whitelist, so `run` treated `classify` as a provider slug and sent it
+  to `/apis/v1/classify` — a 404 with "api endpoint not found". The whitelist
+  is now pinned to the server's route table by a test that lists every
+  registered `/v1` segment.
+- **Every `aisa skills` subcommand except `init` returned nothing.** The
+  registry read only the top level of a repo that nests skills two deep, so it
+  treated the six category directories as skills. Slugs are now derived from
+  `SKILL.md` locations at any depth, all 42 skills are listed, and a bare name
+  (`marketpulse`) resolves to its canonical slug. The repo tree is fetched once
+  per process and cached for an hour instead of being re-fetched per command.
+- **`aisa video create` and `video status` always 404'd.** They called
+  `/apis/v1/services/aigc/...`, a provider that does not exist; the real
+  endpoints are `POST /v1/video/generations` and
+  `GET /v1/video/generations/:task_id`. The default model `wan2.6-t2v` also did
+  not exist. Polling checked for `PENDING`/`RUNNING`, which the current status
+  enum never returns, so `--wait` exited immediately as a failure. Task ids are
+  now the gateway's own `video_task_<hex>` — ids saved from 0.2.2 will report
+  `task not found`, since they never worked in the first place.
+- **`aisa screener` 404'd** — the path was missing its `/screener` suffix and
+  used the wrong method — and it sent an empty filter set, which the upstream
+  rejects.
+- **`aisa web-search` defaulted to a broken backend.** `smart` and `full` return
+  an upstream 404 for every parameter shape; the default is now `tavily`. The
+  same stale example was baked into the `skills init` search template, which
+  would have taught agents to call the broken endpoint.
+- **`aisa crypto` returned `403 Crypto access restricted`.** It now uses the
+  coingecko provider, which is healthy and cheaper, with a symbol → coin-id
+  table; ambiguous symbols list candidates instead of guessing.
+- **`aisa config set baseUrl` only affected half the requests.** Integration
+  calls hardcoded their base. All three bases are now derived from one root,
+  and `config list` shows what they resolve to. Existing configs holding the
+  historical `https://api.aisa.one/v1` default keep working.
+- **`aisa skills install` now replaces the target directory instead of merging
+  into it**, so a previous skill's scripts and assets cannot linger and keep
+  being loaded by an agent. A partial download aborts the whole install and
+  leaves the existing directory untouched, rather than replacing a working
+  skill with an incomplete one. Installs record the canonical slug in
+  `.aisa-skill.json`: frontmatter `name:` is not an identity, and two skills in
+  different categories sharing a leaf name would otherwise overwrite each other
+  silently. `aisa skills remove <category>/<name>` checks that marker before
+  deleting, so it cannot take out a same-named skill from another category.
+  Naming a category means "this specific skill", so both install and remove
+  refuse to touch a directory whose ownership they cannot verify — including
+  ones installed before markers existed; `--force` overrides. A bare name still
+  works unguarded, since it only resolves when the leaf name is unique.
+- Binary files in a skill (images, fonts) are no longer corrupted on install by
+  a UTF-8 round trip.
+- Sub-cent prices no longer display as `$0.00` — real catalog values go down to
+  `$0.000001`.
+
+### Changed
+
+- `aisa api code` defaults to `--lang curl` (was `typescript`) and never
+  interpolates your real key — snippets read `AISA_API_KEY` from the
+  environment. The catalog reports every method as `GET` server-side, so the
+  generated method is advisory; use `--method` to override.
+- `tests/` is no longer published to npm (the package now ships an explicit
+  `files` allowlist), and `npm run build` cleans `dist/` first so stale
+  artefacts cannot ship.
+
+### Known issues
+
+- **`aisa usage` still reports that the API is unavailable.** The gateway does
+  not serve `GET /v1/credits/usage` — it 404s in production even though
+  `/v1/credits/balance` on the same route group works. The CLI side is
+  unblocked and will be wired up once that route ships.
+- `aisa mcp setup` writes `https://docs.aisa.one/mcp`, a domain with no DNS
+  record, and **overwrites your agent's MCP config if it cannot parse it** —
+  a file with comments or a trailing comma will be emptied. This release does
+  not touch the MCP commands; avoid `aisa mcp setup` until it is fixed.
+- `web-search --type smart` and `--type full` remain degraded upstream.
+
 ## [0.2.2] — 2026-08-03
 
 ### Added
@@ -66,7 +217,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Config commands (`aisa config get|set|list|reset`) and auth
   (`aisa login|logout|whoami`).
 
-[Unreleased]: https://github.com/AIsa-team/cli/compare/v0.2.2...HEAD
+[Unreleased]: https://github.com/AIsa-team/cli/compare/v0.2.4...HEAD
+[0.2.4]: https://github.com/AIsa-team/cli/compare/v0.2.3...v0.2.4
+[0.2.3]: https://github.com/AIsa-team/cli/compare/v0.2.2...v0.2.3
 [0.2.2]: https://github.com/AIsa-team/cli/compare/v0.2.1...v0.2.2
 [0.2.1]: https://github.com/AIsa-team/cli/releases/tag/v0.2.1
 [0.2.0]: https://github.com/AIsa-team/cli/releases/tag/v0.2.0

package/README.md

@@ -1,6 +1,8 @@
 # @aisa-one/cli
 
-CLI for the [AISA](https://aisa.one) unified AI infrastructure platform. Access 70+ LLMs, web search, financial data, Twitter/X, and video generation APIs — all from one command line.
+Command-line access to [AIsa](https://aisa.one): **one API key for 80+ LLMs and
+950+ endpoints** across 29 API providers — finance, web search, social,
+research, and video generation.
 
 ## Install
 
@@ -11,130 +13,219 @@ npm install -g @aisa-one/cli
 ## Quick Start
 
 ```bash
-# Authenticate
+# Authenticate (or set AISA_API_KEY)
 aisa login --key sk-your-api-key
 
-# Chat with any LLM
+# See what's available — no API key needed for this part
+aisa api list
+aisa api search "insider trades"
+
+# Chat with any model
 aisa chat "Explain quantum computing" --model claude-opus-4-6
 
+# Look up a stock
+aisa stock AAPL
+
 # Search the web
 aisa web-search "latest AI research"
 
-# Look up stock data
-aisa stock AAPL
+# Call any endpoint in the catalog directly
+aisa run financial /insider-trades -q "ticker=AAPL"
+```
+
+Get your API key at
+[console.aisa.one/api-keys](https://console.aisa.one/api-keys). New accounts
+receive $5 in free credits.
+
+## API Catalog
+
+The catalog is the fastest way to find what the platform can do. It reads a
+public endpoint, so `list`, `show`, `search`, and `code` all work before you log
+in.
 
-# Post a tweet
-aisa tweet "Hello from AISA CLI!"
+```bash
+aisa api list                          # all 29 providers
+aisa api list --category finance       # finance, search, social, productivity, other
+aisa api list --health                 # include provider health
+
+aisa api show financial                # every endpoint in one provider
+aisa api show financial /news          # one endpoint: params, price, run command
+aisa api show dataforseo --all         # 453 endpoints (truncated to 40 by default)
+
+aisa api search "stock screener"       # search across all 950+ endpoints
+aisa api search rank --provider dataforseo
 
-# Generate a video
-aisa video create "A cat playing piano" --wait
+aisa api code financial /news --lang curl     # curl, python, node, typescript
 ```
 
-Get your API key at [aisa.one/dashboard](https://aisa.one/dashboard). New accounts receive $5 in free credits.
+Two things worth knowing: a provider's **id is not always its URL slug** —
+`brave-search` serves `/apis/v1/brave/...`, and `api show` prints the path you
+actually call. And the catalog reports every method as `GET`; pass `--method` to
+`api code` when an endpoint takes a POST.
 
-## Commands
+The catalog is cached in `~/.aisa/cache` (override with `AISA_CACHE_DIR`). Pass
+`--refresh` to any command to bypass it, or `aisa cache clear`.
 
-### Authentication
+## Execute Any Endpoint
 
 ```bash
-aisa login --key <key>    # Store API key (also reads AISA_API_KEY env var)
-aisa logout               # Remove stored key
-aisa whoami               # Show auth status
+aisa run financial /insider-trades -q "ticker=AAPL"
+aisa run coingecko /simple/price -q "ids=bitcoin&vs_currencies=usd"
+aisa run brave /web/search -q "q=AI agents"
+aisa run tavily /search -d '{"query": "AI news"}'
+aisa run twitter /tweet/advanced_search -q "query=AI agents" --raw
+aisa run dataforseo /serp/google/organic/live -d '{...}' --show-cost
 ```
 
-### LLM Gateway
+`run` sends anything that isn't a known LLM gateway route to the integration
+APIs, so providers added to the platform work without a CLI upgrade. Use
+`--llm` or `--domain` to force a base.
+
+`--show-cost` prints the gateway's billing headers on stderr, so it stays out of
+the way of `--raw | jq`. Metered providers (DataForSEO, Jina) report the amount
+actually charged and the credits consumed — for those the catalog's flat
+per-request price is not what you pay. Other routes report only a price key, and
+the LLM gateway reports nothing; the output says so rather than implying a call
+was free.
 
-Chat with 70+ models (GPT, Claude, Gemini, Qwen, Deepseek, Grok) through a single OpenAI-compatible endpoint.
+## LLM Gateway
+
+80+ models (GPT, Claude, Gemini, Qwen, Deepseek, Grok) behind one
+OpenAI-compatible endpoint.
 
 ```bash
 aisa chat "your message" --model gpt-4.1-mini
-aisa chat "explain this" --model claude-opus-4-6 --stream
+aisa chat "explain this" --model claude-opus-4-6
 aisa chat "respond in JSON" --model gemini-2.5-pro --json
-echo "summarize this" | aisa chat                        # pipe support
+echo "summarize this" | aisa chat                  # pipe support
 
 aisa models                          # list all models
 aisa models --provider anthropic     # filter by provider
 aisa models show gpt-4.1-mini        # model details
 ```
 
-### API Discovery & Execution
+Streaming is on by default; pass `--no-stream` to disable it.
+
+## Finance
 
 ```bash
-aisa api list                                # 🚧 WIP — not yet available
-aisa api search "email finder"               # 🚧 WIP
-aisa api show finance /stock/price           # 🚧 WIP
-aisa api code finance /stock/price --lang python  # 🚧 WIP
+aisa stock AAPL                     # summary: company info + estimates + news
+aisa stock AAPL --field insider     # insider trades
+aisa stock AAPL --field news        # company news
+aisa stock TSLA --field filings     # SEC filings
+aisa stock MSFT --field estimates   # analyst EPS & revenue estimates
+aisa stock AAPL --field financials  # balance sheets, income statements
 
-# Execute any API (works now)
-aisa run financial /insider-trades -q "ticker=AAPL"
-aisa run tavily /search -d '{"query": "AI news"}'
-aisa run twitter /tweet/advanced_search -q "query=AI agents" --raw
+aisa crypto BTC                     # price, 24h change, market cap
+aisa crypto ETH --period 30d        # historical
+aisa crypto --id render-token RNDR  # exact CoinGecko id when a symbol is ambiguous
+
+aisa screener --sector "Information Technology"
+aisa screener --min-market-cap 1000000000000 --limit 10
+aisa screener --filter market_cap:gt:1e12 --filter sector:eq:Financials
 ```
 
-### Web Search
+Sectors use GICS names; short forms like `Technology` are mapped automatically.
+
+## Web Search
 
 ```bash
-aisa web-search "query"                     # smart search (default)
-aisa web-search "query" --type full         # full-text search
+aisa web-search "query"                     # Tavily (default)
 aisa web-search "query" --type youtube      # YouTube search
-aisa web-search "query" --type tavily       # Tavily deep search
 aisa scholar "transformer architecture"     # academic papers
 ```
 
-### Finance
-
-```bash
-aisa stock AAPL                     # summary: company info + estimates + news
-aisa stock AAPL --field insider     # insider trades
-aisa stock AAPL --field news        # company news
-aisa stock TSLA --field filings     # SEC filings
-aisa stock MSFT --field estimates   # analyst EPS & revenue estimates
-aisa stock AAPL --field financials  # balance sheets, income statements
-aisa crypto BTC                     # crypto price snapshot
-aisa crypto ETH --period 30d       # historical
-aisa screener --sector Technology   # stock screener
-```
+`--type smart` and `--type full` are currently degraded upstream and return 404
+regardless of parameters. Use `tavily` until that is resolved.
 
-### Twitter/X
+## Twitter/X
 
 ```bash
 aisa twitter user elonmusk                  # user profile
 aisa twitter search "AI agents" --limit 20  # search tweets
 aisa twitter trends                         # trending topics
-aisa tweet "Hello world!"                   # post (⚠️ requires login cookies, see docs)
+aisa twitter user-tweets elonmusk           # recent tweets
+aisa twitter thread <tweet-id>              # full conversation
 ```
 
-### Video Generation
+Read operations work with just your API key. **Write operations** (`aisa tweet`,
+`like`, `retweet`, `follow`, `dm`) additionally require Twitter login cookies
+and a proxy — run `aisa twitter login --username <u> --password <p> --proxy <url>`
+first. Run `aisa twitter --help` for the full list of 30+ subcommands.
+
+## Video Generation
 
 ```bash
-aisa video create "A sunset timelapse"           # create task
-aisa video create "Dancing robot" --wait         # wait for result
-aisa video status <task-id>                      # check status
+aisa video create "A sunset timelapse"                  # returns a task id
+aisa video create "Dancing robot" --wait                # poll until done
+aisa video create "A cat" --output cat.mp4              # wait and download
+aisa video status <task-id>
+
+# image-to-video: --image is shorthand for --media first_frame=<url>
+aisa video create "the bird turns its head" --model wan2.7-i2v --image https://…/photo.jpg
+aisa video create "extend this clip" --model wan2.7-r2v --media first_clip=https://…/in.mp4
+
+# Seedance uses a different request shape; the CLI handles it
+aisa video create "a cat walking" --model dreamina-seedance-2-0-fast-260128
 ```
 
-### Account
+| Model | Needs | Billing |
+|-------|-------|---------|
+| `wan2.7-t2v` (default), `happyhorse-1.1-t2v` | prompt only | per second |
+| `wan2.7-i2v`, `happyhorse-1.1-i2v` | `--image` / `--media first_frame=` | per second |
+| `wan2.7-r2v`, `happyhorse-1.1-r2v` | `--media first_clip=` | per second |
+| `dreamina-seedance-2-0-260128`, `…-fast-260128` | prompt only | per token |
+
+Media types: `first_frame`, `last_frame`, `driving_audio`, `first_clip`.
+
+The gateway forwards the request body to whichever vendor owns the model, so the
+shape differs per family — the CLI builds it for you and refuses up front if a
+model needs source media you did not supply (the upstream would otherwise accept
+the job, bill it, and fail a minute later). For a vendor or parameter the CLI
+does not model, `--body '<json>'` is sent verbatim.
+
+## Account
 
 ```bash
-aisa balance                # Show wallet and API key credit balance
-aisa balance --json         # Output the balance response as JSON
-aisa usage --limit 20       # 🚧 WIP
+aisa balance                        # wallet and API key credit balance
+aisa balance --json
 ```
 
-## Skills
+`aisa usage` is not available yet — the gateway does not serve
+`GET /v1/credits/usage` (it 404s, while `/v1/credits/balance` on the same route
+group works). Use the [console](https://console.aisa.one/logs) for usage history
+in the meantime.
 
-Skills are markdown files that teach AI coding agents (Claude Code, Cursor, Copilot, etc.) how to use AISA APIs. Skills are sourced from the [agent-skills](https://github.com/AIsa-team/agent-skills) repository.
+## Skills
 
-### Browse & Install
+Skills are markdown files that teach AI coding agents (Claude Code, Cursor,
+Copilot, …) how to use AIsa APIs. They come from the
+[agent-skills](https://github.com/AIsa-team/agent-skills) repository — 42 skills
+across six categories.
 
 ```bash
-aisa skills list                              # list all available skills
-aisa skills search "financial analysis"       # search by keyword
-aisa skills show marketpulse                  # show skill details
-aisa skills install marketpulse               # install to agent directories
-aisa skills remove marketpulse                # uninstall
+aisa skills list                              # all skills
+aisa skills list --category financial         # one category
+aisa skills search "financial analysis"
+aisa skills show marketpulse                  # bare name or financial/marketpulse
+aisa skills install marketpulse               # install to detected agent directories
+aisa skills install marketpulse --force       # replace whatever occupies that directory
+aisa skills remove marketpulse
 ```
 
-Skills install to agent directories automatically:
+Installing replaces the target directory rather than merging into it, so a
+previous skill's scripts and assets cannot linger and keep being loaded, and a
+partial download aborts without touching what is already there. Each install
+writes a small `.aisa-skill.json` recording which skill owns the directory —
+that marker is what lets the CLI tell two same-named skills apart.
+
+Naming a category (`financial/marketpulse`) means "this specific skill", so the
+CLI checks the marker before replacing or removing anything. A directory
+installed before markers existed cannot be verified that way, so those need
+`--force`. A bare name (`marketpulse`) means "whatever holds that directory" and
+always works — it only resolves when the leaf name is unique across the repo.
+
+Skills install to whichever agent directories exist on your machine:
 
 | Agent | Directory |
 |-------|-----------|
@@ -149,45 +240,80 @@ Skills install to agent directories automatically:
 ### Create Skills
 
 ```bash
-aisa skills init my-skill                          # create from default template
-aisa skills init my-skill --template finance       # finance template
-aisa skills init my-skill --template llm           # LLM template
+aisa skills init my-skill                          # default template
+aisa skills init my-skill --template finance       # finance, llm, search, twitter, video
 ```
 
-Available templates: `default`, `llm`, `search`, `finance`, `twitter`, `video`
-
-To publish a skill, submit a pull request to [AIsa-team/agent-skills](https://github.com/AIsa-team/agent-skills).
+To publish a skill, open a pull request against
+[AIsa-team/agent-skills](https://github.com/AIsa-team/agent-skills).
 
 ## MCP Server
 
-Auto-configure AISA's MCP server for your AI agents:
-
 ```bash
-aisa mcp setup                          # configure all detected agents
-aisa mcp setup --agent cursor           # Cursor only
-aisa mcp setup --agent claude-desktop   # Claude Desktop only
+aisa mcp setup                          # configure detected agents
 aisa mcp status                         # check configuration
 ```
 
+> **Not currently usable.** These commands write
+> `https://docs.aisa.one/mcp`, which has no DNS record, and `mcp setup`
+> overwrites an agent config file it cannot parse — a `mcp.json` with comments
+> or a trailing comma will be emptied. Avoid `aisa mcp setup` until this is
+> fixed.
+
+## Shell Completion
+
+```bash
+# zsh
+aisa completion zsh > "${fpath[1]}/_aisa"      # then restart your shell
+# or, without touching fpath:
+echo 'eval "$(aisa completion zsh)"' >> ~/.zshrc
+
+# bash
+aisa completion bash > /usr/local/etc/bash_completion.d/aisa
+# or:
+echo 'eval "$(aisa completion bash)"' >> ~/.bashrc
+
+# fish
+aisa completion fish > ~/.config/fish/completions/aisa.fish
+```
+
+`aisa completion` with no argument detects your shell from `$SHELL`.
+
+Completion covers commands, subcommands, and options, plus values pulled from
+the local cache:
+
+```
+aisa run <TAB>                 → 29 provider slugs
+aisa run financial <TAB>       → that provider's endpoints
+aisa api show <TAB>            → provider ids
+aisa skills show <TAB>         → 42 skill names
+aisa chat --model <TAB>        → model ids
+aisa web-search --type <TAB>   → tavily, youtube, scholar, …
+```
+
+The cache-backed suggestions only appear once the relevant command has been run
+at least once — completion never makes a network request, so a cold cache
+completes commands and flags but no dynamic values. Run `aisa api list`,
+`aisa models`, and `aisa skills list` once to warm everything up.
+
 ## Configuration
 
 ```bash
-aisa config set defaultModel claude-opus-4-6   # change default model
-aisa config get defaultModel                    # read a value
-aisa config list                                # show all settings
-aisa config reset                               # reset to defaults
+aisa config set defaultModel claude-opus-4-6
+aisa config get defaultModel
+aisa config list                                # also shows derived base URLs
+aisa config reset
 ```
 
 Settings:
 - `defaultModel` — default model for `aisa chat` (default: `gpt-4.1-mini`)
-- `baseUrl` — API base URL (default: `https://api.aisa.one`)
-- `outputFormat` — output format: `text` or `json`
-
-Environment variable `AISA_API_KEY` takes precedence over stored key.
+- `baseUrl` — platform root; the LLM (`/v1`), integration (`/apis/v1`), and
+  catalog bases are all derived from it
+- `outputFormat` — `text` or `json`
 
-## Known Issues
-
-**GPT-4.1 streaming returns empty output.** The AISA gateway currently strips `choices[].delta.content` from GPT model SSE chunks, so streaming mode produces blank output for GPT models. Workaround: use `--no-stream` or switch to Claude/Qwen models which stream correctly. Non-streaming GPT works fine.
+Environment variables: `AISA_API_KEY` takes precedence over the stored key.
+`AISA_CACHE_DIR` relocates the cache. `GITHUB_TOKEN` raises the GitHub rate
+limit for skills commands.
 
 ## Development
 
@@ -200,23 +326,44 @@ npm run dev         # watch mode
 npm test            # run tests
 ```
 
-## Appendix: Architecture Notes for Contributors
-
-**Two base URLs.** The AISA platform uses separate base paths:
-- LLM endpoints (chat, models): `https://api.aisa.one/v1/`
-- Domain API endpoints (search, finance, twitter, video): `https://api.aisa.one/apis/v1/`
-
-The `domain: true` option in `RequestOptions` (see `src/api.ts`) selects which base URL to use. The `run` command auto-detects based on the slug prefix.
-
-**Parameter naming varies by endpoint.** Smart/full search uses `q`, scholar uses `query`, finance uses `ticker` (not `symbol`), Twitter uses `userName` (camelCase). Always check the [API Reference](https://docs.aisa.one/reference) for exact parameter names.
-
-**Video generation is async.** POST to `/services/aigc/video-generation/video-synthesis` with header `X-DashScope-Async: enable`, then poll `GET /services/aigc/tasks?task_id=<id>` for status. Response shape uses `output.task_id`, `output.task_status`, `output.video_url`.
-
-**Twitter write operations require login cookies.** `create_tweet_v2` and other action endpoints need `login_cookies` and `proxy` fields — they don't work with just the API key.
-
-**Models API follows OpenAI format.** The `/v1/models` endpoint returns `owned_by` (not `provider`) and has no `name`, `pricing`, or `contextWindow` fields.
-
-**Some financial endpoints return empty data.** `financial/prices` and `financial/financial-metrics/snapshot` return `{}` for all tickers (backend issue). The default `aisa stock` now fetches `company/facts` + `analyst-estimates` + `news` instead. Working fields: `info`, `estimates`, `financials`, `filings`, `insider`, `institutional`, `news`.
+## Appendix: Notes for Contributors
+
+**Three bases, one root.** `resolveBases()` in `src/api.ts` derives the LLM base
+(`/v1`), the integration base (`/apis/v1`), and the catalog root from a single
+configured `baseUrl`. It tolerates a value with either suffix already attached,
+because the shipped default has always included `/v1` and is persisted in every
+existing user's config.
+
+**Routing in `run`.** `resolveRunTarget()` (`src/commands/run.ts`) treats the LLM
+gateway routes as the whitelist and everything else as an integration API. That
+direction matters: gateway routes are hardcoded server-side and change roughly
+annually, while provider slugs are database rows that operations edit
+continuously.
+
+**The catalog's shape has three traps.** `endpoints[].method` is hardcoded to
+`GET` server-side. `endpoint_groups[].name` is an operator-entered label
+(`Zero`, `One`, `default`) with no business meaning, which is why `api show`
+flattens by default. And health is tracked per provider, not per endpoint, so
+per-endpoint counts are one value repeated.
+
+**Parameter naming varies by endpoint.** Scholar uses `query`, finance uses
+`ticker` (not `symbol`), Twitter uses `userName`. `aisa api show <api> <path>`
+prints each endpoint's description and path parameters.
+
+**Video generation is async.** `POST /v1/video/generations` returns `202` with a
+gateway-local `video_task_<hex>` id. Poll `GET /v1/video/generations/:id` until
+`status` is one of `completed`, `failed`, or `cancelled`. The finished URL sits
+at a different place in `result` for each vendor, so `findVideoUrl()` searches
+for it.
+
+**Twitter write operations require login cookies.** `create_tweet_v2` and the
+other action endpoints need `login_cookies` and `proxy` in the body — the
+gateway does not hold your Twitter session.
+
+**Some financial endpoints return empty data.** `financial/prices` and
+`financial/financial-metrics/snapshot` return `{}` for all tickers. `aisa stock`
+uses `company/facts` + `analyst-estimates` + `news` instead. Working fields:
+`info`, `estimates`, `financials`, `filings`, `insider`, `institutional`, `news`.
 
 ## License