| name | aisa-tavily |
| description | Search the web and extract public page content through AIsa's Tavily-backed API relay. Use when: the user needs open-web research, source discovery, current news lookup, or public URL content extraction. Supports concise result sets, deeper research, and news-focused queries. |
| metadata | {"aisa":{"emoji":"🛠","requires":{"bins":["node"],"env":["AISA_API_KEY"]},"primaryEnv":"AISA_API_KEY","compatibility":["openclaw","claude-code","hermes"]},"hermes":{"tags":["research","x","search","aisa"]}} |
| required_environment_variables | [{"name":"AISA_API_KEY","prompt":"AIsa API key","help":"Get your key from https://aisa.one or the AIsa marketplace account panel.","required_for":"AIsa-backed API access"}] |
aisa-tavily
Search the web and extract public page content through AIsa's Tavily-backed API relay. Use when: the user needs open-web research, source discovery, current news lookup, or public URL content extraction. Supports concise result sets, deeper research, and news-focused queries.
When to Use
- Use this release when the user needs the runtime packaged under
scripts/.
- Prefer the bundled Python or shell entrypoints instead of copying raw API examples into the chat.
- For Hermes community installs, keep setup explicit and review the command help text before the first run.
Setup
- Review
README.md for the release-specific summary and structure.
- Use repo-relative paths under
scripts/.
- Prefer explicit CLI auth flags such as
--api-key or --aisa-api-key when a script exposes them.
Verification
- Confirm the command returns structured output or a successful API response.
- If the workflow stores local state, verify it writes under a repo-local data directory rather than a home-directory default.
