Basileus CLI
Deploy and manage autonomous AI agents on Base — from zero to a running self-sustaining agent in one command.
Install
pip install basileus
Commands
basileus deploy
Full end-to-end deployment of a new agent:
- Wallet setup — generates a new Base wallet (or reuses existing from
.env.prod) - Funding — prompts you to send ETH, then auto-swaps to ALEPH (compute) + USDC (inference)
- ENS subdomain — registers
<name>.basileus-agent.ethand setscontentHashfor the dashboard - ERC-8004 identity — uploads metadata to IPFS and registers the agent on-chain
- Aleph Cloud VM — creates a compute instance, sets up Superfluid payment streams (operator + community)
- Code deployment — uploads agent code via SSH, installs Node.js + deps, configures systemd service
basileus deploy [PATH]
| Option | Default | Description |
|---|---|---|
PATH |
. |
Path to agent directory |
--min-eth |
0.02 |
Minimum ETH to wait for before proceeding |
--ssh-key |
auto-detect | Path to SSH public key |
basileus register
Register an already-deployed agent on the ERC-8004 IdentityRegistry. Useful if deployment was interrupted after the VM was created but before on-chain registration completed.
basileus register [PATH]
Requires an existing wallet (.env.prod) and ENS subname.
basileus set-content-hash
Update the ENS contentHash for an agent's subname. Used when the frontend IPFS hash changes and dashboards need to point to the new version.
basileus set-content-hash [PATH]
basileus stop
Tear down a running agent — deletes Aleph Cloud instance and closes Superfluid payment streams.
basileus stop [PATH]
Prompts for confirmation before proceeding. Shows what resources will be deleted.
What Happens Under the Hood
basileus deploy
│
├─ Wallet
│ ├─ Generate keypair (or load from .env.prod)
│ └─ Write WALLET_PRIVATE_KEY + BUILDER_CODE to .env.prod
│
├─ Funding
│ ├─ Wait for ETH deposit to agent address
│ ├─ Swap ETH → ALEPH (~10 tokens for compute)
│ ├─ Swap ETH → USDC (for x402 inference payments)
│ └─ Reserve 0.001 ETH for gas
│
├─ ENS
│ ├─ Register <name>.basileus-agent.eth via L2Registrar
│ └─ Set contentHash (IPFS pointer to dashboard frontend)
│
├─ ERC-8004
│ ├─ Build agent metadata (name, description, services)
│ ├─ Upload metadata to IPFS via Aleph
│ └─ Register on IdentityRegistry (mint agent NFT)
│
├─ Aleph Cloud
│ ├─ Create compute instance on CRN
│ ├─ Compute Superfluid flow rates
│ ├─ Create operator payment stream (ALEPH)
│ ├─ Create community payment stream (ALEPH)
│ ├─ Notify CRN for allocation
│ └─ Wait for instance to come up
│
└─ Code Deployment
├─ Wait for SSH access
├─ Upload agent source code
├─ Install Node.js runtime
├─ Install npm dependencies
├─ Configure systemd service
└─ Verify service is running
Dependencies
- web3.py — Ethereum interactions
- aleph-sdk-python — Aleph Cloud instance management + IPFS
- paramiko — SSH for VM deployment
- typer + rich — CLI interface
Development
cd cli
poetry install
poetry run basileus --help
Metadata
Release files for basileus 0.1.2
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 | |
|---|---|---|---|---|
| basileus-0.1.2.tar.gz | 20.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| basileus-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.2 kB
Release files / basileus-0.1.2.tar.gz
| Download URL | basileus-0.1.2.tar.gz |
|---|---|
| Size | 20.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c1c51af2d728e07bc490694a594a9cf6a753a5e45a20650e46403ed9bb1a503
|
|
BLAKE2b-256 checksum How to use checksums |
7c3f7fe2017997290aefae5adf27f0c7c9d00136845fd3aab4d4860384f605a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 21, 2026.
Transparency logRelease files / basileus-0.1.2-py3-none-any.whl
| Download URL | basileus-0.1.2-py3-none-any.whl |
|---|---|
| Size | 28.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84b576b52e13e8086bf13521d74ede3301c4073e1afdfd665af47a46a6d16741
|
|
BLAKE2b-256 checksum How to use checksums |
567a1dcabf1a02d389edc356c6eec691f234e943944ee7cedfd04532f32bcaee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 21, 2026.
Transparency logSecurity for basileus 0.1.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for basileus-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 21, 2026.
Transparency logA 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.