race-cli
Command-line interface for the Race Engineering GPU cloud platform.
Install
pip install race-ai
Quick start
# Generate an API key first, via the Race Engineering web dashboard
# (Account Settings -> API Keys -> Create Key)
race login --key rk_xxxxxxxxxxxxxxxxxxxxxxxx
race deploy --gpu <slice_id> --template <template_id>
race status <pod_id>
Commands
| Command | Description |
|---|---|
race login --key <key> |
Store an API key locally (OS keychain — never a plaintext file) |
race logout |
Remove the locally stored key |
race deploy --gpu <slice_id> --template <template_id> |
Deploy a new GPU pod |
race list |
List your pods |
race status <pod_id> |
Check a pod's deploy status |
race pause <pod_id> |
Pause a running pod |
race resume <pod_id> |
Resume a paused pod |
race terminate <pod_id> [--yes] |
Terminate a pod (asks for confirmation unless--yes) |
Run race --help or race <command> --help for full option details at any time.
Configuration
By default the CLI talks to the production API. To point it elsewhere (e.g. a self-hosted or staging instance):
race login --key <key> --base-url https://your-instance.example.com
The base URL is remembered for future commands — you don't need to pass it every time.
Authentication & security
- API keys are generated through the web dashboard, not this CLI —
race loginonly stores a key you already have. - Keys are stored using your operating system's credential store (macOS Keychain,
Windows Credential Manager, Linux Secret Service) via the
keyringpackage — never written to a plaintext file on disk. race loginvalidates the key against the API before storing it, so a mistyped or invalid key is never silently saved.
Retries and idempotency
race deploy automatically retries once on a network-layer failure (timeout, dropped
connection) using the same idempotency key for every retry of that attempt — this
guarantees a retried deploy can never accidentally create a second pod. A definitive
error response from the server (e.g. insufficient balance, invalid template) is not
retried.
Requirements
- Python 3.9+
- A Race Engineering account and API key
License
MIT — see LICENSE.
Release files for race-ai 0.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 | |
|---|---|---|---|
| race_ai-0.1.1.tar.gz | 11.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| race_ai-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.1 kB
Release files / race_ai-0.1.1.tar.gz
| Download URL | race_ai-0.1.1.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2de7b41a2062bb7e9ce72dd3edefc54f6af2bc68453ab9b55cd9639106b1a6f2
|
|
BLAKE2b-256 checksum How to use checksums |
0b014386ab7c585ffc47061d8e0a18fa6fde85824fade63f63250f242346c50d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / race_ai-0.1.1-py3-none-any.whl
| Download URL | race_ai-0.1.1-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0522935434528f2599ba656b25f07259d9e2036a28f46e3b202232b878158268
|
|
BLAKE2b-256 checksum How to use checksums |
c4eb0f35baa71e3a893093199b73003d1e1b20174d137d554a9e6cd1d876da69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|