rgba CLI
Thin HTTPS client for the deployed RGBA API (Modal-hosted). The CLI defaults
to the right backend URL; override with RGBA_API_URL for local dev.
Install
pip install rgba # from PyPI
pipx install rgba # isolated user install (recommended for daily use)
After install you'll have a rgba command on your PATH.
Usage
rgba auth login # device-flow → opens https://rgba.ai/cli in your browser
rgba auth status # show whoami
rgba auth logout # revoke the active token
rgba me # alias for `auth status`
rgba actions # discover every /sdk/action with cost + params
rgba actions <name> # full schema for one action
rgba sdk <action> -p key=val # call /sdk/action
rgba jobs get <job_id> # poll a job
rgba jobs wait <job_id> # poll until status is completed/failed
rgba actions social-publish -p operation=channels # connected social accounts
rgba actions social-publish --params-file publish.json # draft/post/schedule video
Credentials live in ~/.rgba/credentials (mode 0600). The CLI never sees
your Supabase password — auth is brokered through a device-flow OAuth
against the RGBA backend.
Publish videos
Video publishing supports YouTube, Instagram, and TikTok through Postiz. In RGBA, open Settings → Connect Postiz, save your Postiz workspace API key, and connect your social accounts. Multiple channels are supported. The key stays on the server; do not pass it to the CLI.
Run rgba actions social-publish -p operation=channels to find channel IDs.
For a YouTube draft, save this as publish.json with your channel ID and a
public HTTPS video file URL:
{
"operation": "publish",
"request_id": "my-video-001",
"video_url": "https://your-cdn.example/video.mp4",
"mode": "draft",
"targets": [{
"channel_id": "YOUR_CHANNEL_ID",
"content": "My video description",
"settings": {"title": "My video", "type": "private", "selfDeclaredMadeForKids": "no"}
}]
}
Then run rgba actions social-publish --params-file publish.json.
Local files can first use rgba actions upload -p file_path=/path/video.mp4;
use the returned URL. An owned RGBA video's video_id can replace video_url.
Publishing defaults to a draft; use mode=now or mode=schedule with a
timezone-aware publish_at for authorized automation. Reuse the same
request_id and parameters on retries to avoid duplicate submissions.
An accepted receipt means Postiz accepted the submission; use
operation=posts with start_date and end_date to check delivery.
Run rgba actions social-publish for the full action schema.
Environment
| var | default | use |
|---|---|---|
RGBA_API_URL |
https://lemontree-media-llc--rgba-agent-agent-app.modal.run |
Override the API origin (e.g. localhost) |
RGBA_CONFIG_DIR |
~/.rgba |
Override credentials directory |
Metadata
Release files for rgba 0.3.5
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 | |
|---|---|---|---|---|
| rgba-0.3.5.tar.gz | 63.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rgba-0.3.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 135.8 kB
Release files / rgba-0.3.5.tar.gz
| Download URL | rgba-0.3.5.tar.gz |
|---|---|
| Size | 63.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b481134f21d90f1cd411a9f60838adff1a91408f3bdbccb6bdbb37aea15f91a
|
|
BLAKE2b-256 checksum How to use checksums |
88eebe03f15fe9339a5f01f7be45c0980dc865a916c95d9e9c0c6c0599852823
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / rgba-0.3.5-py3-none-any.whl
| Download URL | rgba-0.3.5-py3-none-any.whl |
|---|---|
| Size | 72.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
17ba82890be92b8cfee8c389056e85bcb174fe62ad37b123723c99ebaf5c316a
|
|
BLAKE2b-256 checksum How to use checksums |
201ad4f6b1a8050832aec1e26f5cd290cb71c2ef094b93e1a8175ffa35c5f7e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for rgba 0.3.5
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.