CAAS
Companion as a Service
A terminal-native Solana companion for Pump.fun trading, wallet management, and conversational command execution.
CAAS is designed to feel like a sessioned assistant it remembers state, gates your wallet, shows live balances, and lets you trade or talk naturally from a single CLI.
Install
pip install caas-cli
First-Time Setup
caas init
This walks you through:
- Solana RPC configuration
- Anthropic API key (stored in OS keychain)
- Solana wallet (masked input, Windows-safe)
Wallet Gate (Safety Layer)
Before any trade, your wallet must be unlocked:
caas unlock
- Unlocks wallet in-memory for 30 minutes by default
- Automatically re-locks after TTL
- Manually lock anytime:
caas lock wallet
This is a convenience gate not encryption. Use responsibly.
Trading (Pump.fun)
Buy tokens with SOL:
caas buy --solana 1 <mint>
Sell tokens:
caas sell --solana "25%" <mint>
caas sell --solana all <mint>
Features:
- Slippage + priority fee control
- Pool selection (
pump,auto, etc.) - Spinner-wrapped transactions
- Clean success / warning output
Portfolio & Status
View Saved Keys:
caas show keys
View full portfolio:
caas show port
Check overall status:
caas status
Shows:
- RPC
- Anthropic key
- Wallet state
- Unlock gate
- Slippage / fees / pool
Configuration Commands
caas set rpc
caas set anthropic
caas set wallet
caas set wallet-file <path>
caas set slippage
caas set priority-fee
caas set pool
All secrets are stored securely via OS keychain.
Companion Mode
Start an interactive session:
caas start
In companion mode you can:
- Talk normally
- Issue commands like
buy,sell,status - Let CAAS manage context and state across turns
This is where the Companion part lives.
Reset Everything
caas reset
Clears:
- Config
- Wallet gate
- Stored secrets
Help
caas help
Shows the full rich, in-terminal help panel.
Notes
- Built with Typer + Rich for a native terminal UX
- Wallet value + portfolio fetched via a secure proxy (no API keys shipped)
- Designed for fast iteration, not babysitting
Metadata
Release files for caas-cli 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| caas_cli-1.1.1.tar.gz | 23.4 kB | Without provenance | Details for caas_cli-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| caas_cli-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for caas_cli-1.1.1-py3-none-any.whl |
Total release size: 50.7 kB
Release files / caas_cli-1.1.1.tar.gz
| Download URL | caas_cli-1.1.1.tar.gz |
|---|---|
| Size | 23.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7baa546e3e27543b2de0711086fd5e49696b3934a6dde77b7c3c020f594bdba
|
|
BLAKE2b-256 checksum How to use checksums |
1072ed8846ffd2aac3d99aefd7f1c20cc345637515e95ca2f074ad534511a843
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.13
|
Release files / caas_cli-1.1.1-py3-none-any.whl
| Download URL | caas_cli-1.1.1-py3-none-any.whl |
|---|---|
| Size | 27.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38cb1fdfffb6ab9b89b2e948b95a17332393de91ef04a385a735757895fd23ff
|
|
BLAKE2b-256 checksum How to use checksums |
971fefb082bea61e26ca55b9e5a2a3f3d4b556c34ad4668a4f402bd826f11d70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.13
|
Security for caas-cli 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.