SDK & CLI Overview
Velerion ships one command line tool and a small set of typed client libraries. They are thin wrappers over the same public HTTP API, so nothing in the Console is unreachable from code.
What to use when
Section titled “What to use when”| Task | Reach for |
|---|---|
| Define and deploy an agent | SDK + CLI (velerion deploy) |
| Call a deployed agent from an application | SDK |
| Wire deployment into CI | CLI with a service-account token |
| One-off inspection or debugging | CLI |
| Streaming a response to a browser | SDK server-side, forwarding the stream |
Availability
Section titled “Availability”| Package | Status | Install |
|---|---|---|
@velerion/cli |
stable | npm install -g @velerion/cli |
@velerion/sdk (TypeScript) |
stable | npm install @velerion/sdk |
velerion (Python) |
beta | pip install velerion |
velerion-go |
preview | go get github.com/velerion/velerion-go |
Authentication
Section titled “Authentication”All clients read credentials in the same precedence order:
- An explicit value passed in code, for example
new Velerion({ token }). - The
VELERION_TOKENenvironment variable. - The local CLI session created by
velerion login(~/.config/velerion/credentials.json).
Next steps
Section titled “Next steps”- TypeScript SDK — defining agents and calling them.
- CLI Reference — every command, grouped by area.
