The agents-frame CLI is a thin wrapper over the REST API. It’s the fastest way to feel the router without writing any code, and it’s useful as glue inside shell pipelines, makefiles, and CI jobs.

​
Install

npm install -g agents-frame
The package ships a single binary, agents-frame. Node 18+ is required.

​
Authenticate

Set your API key as an environment variable: 
export AGENTS_FRAME_API_KEY=sk-...
You can also pass --api-key <key> per call, but env var is the recommended path for anything beyond a one-off test.

​
Commands

​
agents-frame route <intent>

Runs /v1/think and prints the selected framework’s promptMd to stdout. 
agents-frame route "decide whether to refactor or rewrite this legacy module"
Flags:
FlagDefaultDescription
--lang <en|zh>autoOverride language detection.
--top-k <n>3Number of candidates to consider.
--recall-k <n>16pgvector recall pool size.
--exclude <slug,...>—Comma-separated framework slugs to exclude.
--jsonoffPrint the raw RouteResult instead of promptMd.
--api-key <key>envOverride AGENTS_FRAME_API_KEY.

​
Recipes

Pipe the framework prompt straight into another LLM call: 
agents-frame route "plan a 3-day product launch" \
  | claude -p "Apply this thinking framework to: launch agents-frame V0"
Get structured JSON for scripting: 
agents-frame route "debug a flaky CI test" --json | jq '.selected.slug'
Force Chinese routing even if the intent is mixed: 
agents-frame route "决策：要不要重写这个老旧模块" --lang zh

​
Exit codes

CodeMeaning
0Success.
1Bad arguments / usage error.
2Auth failed (missing/invalid API key).
3Quota exceeded (HTTP 429).
10Network or server error.

​
Source

The CLI is open development at agentsframe/agents-frame-cli. It’s a thin shim — all the routing logic lives behind the REST endpoint, so the CLI version mostly tracks UX changes (flags, output formats) rather than engine changes.