Getting started
The Workbench CLI, wb, lets you call your company's connections (DigiKey, Mouser, Anthropic, OpenAI, GitLab and the others) from a terminal, a script or your own app, with your company's keys. The keys stay in Workbench: you sign in as yourself, and Workbench adds the key on the server.
During the trial, the CLI is for company admins, in companies where Workbench has turned it on.
Install
You need Node.js 22 or later.
npm install -g https://wbench.io/cli/latest.tgz
Check it:
wb --help
Sign in
wb login
wb login opens Workbench's sign-in page in your browser and prints a short code. Sign in with your usual Workbench account, check that the page shows the same code, and press Authorise. The CLI receives a personal token, keeps it in the macOS keychain, and is signed in.
The token lasts 90 days. You can see it, and revoke it, in Workbench under Developer › Settings › Personal tokens.
Check who you are
wb whoami
It prints your name, your company, your role and when the token expires.
Make your first call
List what your company has:
wb connections
Then call one. This asks DigiKey for a part:
wb call digikey products/v4/search/keyword --data '{"Keywords": "MMBT3904", "Limit": 5}'
The path and the body are DigiKey's own: each connection's page shows its base URL and examples.
Next
- How it works: where the keys live, spend limits and logging.
- CLI reference: every
wbcommand. - Recipes: DigiKey, MRPeasy and a model call, step by step.
- Using the token in your own app: the same calls from Python, TypeScript or curl.
- From Claude Code: the Workbench MCP server.
- Limits and errors: every reason a call is refused.