agoralia-cli
The Agoralia CLI — the third agent surface (alongside MCP and the REST API) for running compliant AI voice campaigns. It's a thin client over the already-gated REST API: same policy, same human-approval flow, same audit. It adds nothing privileged — the gate lives server-side; the CLI just speaks HTTP to it and renders the guided errors it returns.
Every call is tagged X-Agent-Surface: cli, so the action audit records that it came from
the CLI.
Install
pip install agoralia-cli
Authenticate
The CLI uses a Bearer token (the same kind the MCP surface uses).
export AGORALIA_TOKEN=... # your Agoralia access token
export AGORALIA_API_URL=https://api.agoralia.app # optional (defaults to localhost:8000)
Usage
# Generative dashboard pages (the agent composes a view; you see it at /pages/<slug>)
agoralia pages list
agoralia pages get q2-reactivation-calls
agoralia pages create ./spec.json
# Human "go" queue — approve/deny dangerous agent actions
agoralia approvals list
agoralia approvals decide <approval-id> approved
# Read-only audit of what your agents did
agoralia activity --limit 50
# Generic escape hatch to any gated route
agoralia call GET /campaigns
agoralia call POST /campaigns/<id>/start --data '{}'
The approval flow
Dangerous actions (launching a campaign, spending, deleting) are gated. When you hit one without an approval, the CLI tells you exactly what to do:
$ agoralia call POST /campaigns/abc/start
⚠ Approval required before this action can run.
approval_id: appr_123
→ A human must approve it (POST /approvals/{id}/decide), then retry with header X-Approval-Id.
Once approved, retry with: --approval-id appr_123
# a human approves it…
$ agoralia approvals decide appr_123 approved
# …then retry
$ agoralia call POST /campaigns/abc/start --approval-id appr_123
(Approval enforcement is controlled server-side by the AGENT_APPROVAL_ENABLED flag.)
Development
pip install -e .
python -m pytest tests/
python -m agoralia_cli --help # same as the `agoralia` command
Metadata
Release files for agoralia-cli 0.1.0
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 | |
|---|---|---|---|---|
| agoralia_cli-0.1.0.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agoralia_cli-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.4 kB
Release files / agoralia_cli-0.1.0.tar.gz
| Download URL | agoralia_cli-0.1.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ca24302fd3af7b057ef9abda9ccd06e21b436af081ed9d8241cf7a873436820
|
|
BLAKE2b-256 checksum How to use checksums |
dc1477bf3b4982fa8a968a5cd393cfaa65e51d1c13cfdec3624501ca42fcf0d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.0
|
Release files / agoralia_cli-0.1.0-py3-none-any.whl
| Download URL | agoralia_cli-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f64de9fb0fbaf3bf2cfa3b588b9e881d90f1078f004628c367ab37c5fd82c64a
|
|
BLAKE2b-256 checksum How to use checksums |
1a93ac90012997aae5d521c03b89a7a6f8ae797f434254d4171650fe51025960
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.0
|
Security for agoralia-cli 0.1.0
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.