@aisa-plugins/easy-search

Configuration

Setting	Default	Purpose
Routing mode	aisa	aisa, byok, or hybrid
AIsa key reference	AISA_API_KEY	One Key credential
AIsa base URL	https://api.aisa.one	Origin used only for AIsa routes
Tavily key reference	TAVILY_API_KEY	Direct web and extraction
X token reference	X_BEARER_TOKEN	Direct X recent search
YouTube key reference	YOUTUBE_API_KEY	Direct YouTube search
SerpApi key reference	SERPAPI_API_KEY	Direct Scholar search
Request timeout	30000 ms	Per-request cooperative timeout
Response limit	5 MiB	Maximum upstream response bytes
Default results	5	Results retained per selected source
Maximum results	10	User-selectable per-source ceiling
Snippet limit	1200 chars	Maximum normalized preview
Extract limit	100000 chars	Maximum retained content per page

The AIsa base URL must be a credential-free HTTP(S) origin. Direct provider origins are fixed by their adapters and cannot be supplied through tool input.

Headless and managed deployments

The settings card is the normal path, not the only path. Automation can write the same user layer to $DSH_HOME/settings.yaml:

easy-search:
  routingMode: hybrid

The standard local credential provider reads $DSH_HOME/.credentials.yaml:

AISA_API_KEY: your-one-key
TAVILY_API_KEY: your-tavily-key

Keep only the references the deployment needs, preserve unrelated entries, and keep this file at mode 0600 inside an owner-only DSH home. Environment variables with the same names are also supported and take precedence.

Operators can establish a per-profile base in $DSH_HOME/profiles/ /cordis.patch.yml:

- id: easy-search
  config:
    routingMode: hybrid

Do not edit the plugin's installed cordis.patch.yml; package updates may replace package-owned files. DSH watches valid user and profile changes live.