For AI agents: This is the CueAPI CLI. Install with pip install cueapi. Authenticate with cueapi login. Create a cue: cueapi create --name "task-name" --cron "0 9 * * *" --url https://your-handler.com. List cues: cueapi list. View a cue and its recent executions: cueapi get <cue-id>. Your API key can also be set via CUEAPI_API_KEY env var. Do not retry on authentication errors.

CueAPI CLI

Your agents are failing silently. CueAPI tells you when and why.

Cron has no concept of success. Cue does.

The official CLI for CueAPI. Manage your cues, check executions, and verify outcomes from the terminal.

Built for AI builders running agents in production. Schedule your agent tasks, confirm delivery, and verify outcomes without leaving the terminal.

Install

pip install cueapi

Quick start

# Authenticate
cueapi login

# Create your first cue
cueapi create --name "morning-agent-brief" --cron "0 9 * * *" --url https://your-agent.com/run

# See what is scheduled
cueapi list

# Inspect a cue and its recent executions
cueapi get <cue-id>

Why CueAPI over cron?

Cron fires a job. That is it. No retries. No delivery confirmation. No outcome tracking. No visibility.

Feature	Cron	CueAPI
Fires on schedule	Yes	Yes
Confirms delivery	No	Yes
Tracks outcomes	No	Yes
Retries on failure	No	Yes (1, 5, 15 min)
Alerts on failure	No	Yes
Execution history	No	Yes

Commands

Command	Description
`cueapi login`	Authenticate and store API key
`cueapi whoami`	Show current user and plan
`cueapi logout`	Remove local credentials
`cueapi quickstart`	Guided first-cue setup
`cueapi create`	Create a new cue (supports `--worker`, `--payload`, `--on-failure`)
`cueapi list`	List all cues
`cueapi get <id>`	Get cue details and recent executions
`cueapi update <id>`	Update an existing cue
`cueapi pause <id>`	Pause a cue
`cueapi resume <id>`	Resume a cue
`cueapi delete <id>`	Delete a cue
`cueapi fire <id>`	Fire an existing cue immediately, optional `--payload-override`
`cueapi executions list`	List historical executions across all cues
`cueapi executions list-claimable`	List unclaimed worker executions, filter by `--task` / `--agent`
`cueapi executions get <id>`	Fetch one execution by ID
`cueapi executions claim <id> --worker-id ID`	Atomically claim an execution
`cueapi executions claim-next --worker-id ID [--task]`	Claim the next available execution
`cueapi executions heartbeat <id> --worker-id ID`	Extend the claim lease
`cueapi executions report-outcome <id> --success/--failure`	Report a write-once outcome
`cueapi usage`	Show current usage and limits
`cueapi key regenerate`	Regenerate API key
`cueapi upgrade`	Open billing
`cueapi manage`	Open Stripe billing portal

Auth

Credentials stored in ~/.config/cueapi/credentials.json.

Override with env var: export CUEAPI_API_KEY=cue_sk_your_key

Or pass inline: cueapi list --api-key cue_sk_your_key

Transport modes

The CLI works with both webhook and worker cues. For worker cues running without a public URL, install the worker daemon separately:

pip install cueapi-worker

See cueapi-python for the full SDK and worker setup.

Releases

Releases are published to PyPI with PEP 740 attestations via GitHub Actions Trusted Publishing.

License

MIT. See LICENSE.

Built by Vector Apps

Metadata

Release files for cueapi 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cueapi 0.2.0
File	Size	Uploaded	Provenance
cueapi-0.2.0.tar.gz	20.6 kB	May 3, 2026	With provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for cueapi 0.2.0
File	Interpreter	ABI	Platform	Reset
cueapi-0.2.0-py3-none-any.whl 18.2 kB May 3, 2026 With provenance	Python 3	none	any	Details

Total release size: 38.8 kB

Release files / cueapi-0.2.0.tar.gz

Download URL	cueapi-0.2.0.tar.gz
Size	20.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`fb4874066aa2a5b9613f908f829c55ec452bbc8334d22e28fd4c473ed4eeaccc`
BLAKE2b-256 checksum How to use checksums	`eedbbd64c342c12a13e729955a330ebe34e2e59815c3d066998096359a9b169b`
Upload date	May 3, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.13`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/cueapi/cueapi-cli
Publishing commit: github.com/cueapi/cueapi-cli/tree/9220bbb78045b082ac76e34c871e97b85067804a

Workflow

Publishing configuration: github.com/cueapi/cueapi-cli/blob/9220bbb78045b082ac76e34c871e97b85067804a/.github/workflows/publish.yml
Publishing logs: github.com/cueapi/cueapi-cli/actions/runs/25287288167/attempts/1

Artifact

Subject: cueapi-0.2.0.tar.gz
SHA-256 checksum: fb4874066aa2a5b9613f908f829c55ec452bbc8334d22e28fd4c473ed4eeaccc Verifying attestations

Release files / cueapi-0.2.0-py3-none-any.whl

Download URL	cueapi-0.2.0-py3-none-any.whl
Size	18.2 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`9a070bd541268488308cd2b5571be190fcbe74dc171a81ca12a9de8130b3caeb`
BLAKE2b-256 checksum How to use checksums	`74095fe5d2ad308697e18be916a550f7662231f00bd802d48d20e7d979ccac55`
Upload date	May 3, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.13`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/cueapi/cueapi-cli
Publishing commit: github.com/cueapi/cueapi-cli/tree/9220bbb78045b082ac76e34c871e97b85067804a

Workflow

Publishing configuration: github.com/cueapi/cueapi-cli/blob/9220bbb78045b082ac76e34c871e97b85067804a/.github/workflows/publish.yml
Publishing logs: github.com/cueapi/cueapi-cli/actions/runs/25287288167/attempts/1

Artifact

Subject: cueapi-0.2.0-py3-none-any.whl
SHA-256 checksum: 9a070bd541268488308cd2b5571be190fcbe74dc171a81ca12a9de8130b3caeb Verifying attestations

Security for cueapi 0.2.0

Report project as malware

Provenance

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Attestation for cueapi-0.2.0.tar.gz

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/cueapi/cueapi-cli
Publishing commit: github.com/cueapi/cueapi-cli/tree/9220bbb78045b082ac76e34c871e97b85067804a

Workflow

Publishing configuration: github.com/cueapi/cueapi-cli/blob/9220bbb78045b082ac76e34c871e97b85067804a/.github/workflows/publish.yml
Publishing logs: github.com/cueapi/cueapi-cli/actions/runs/25287288167/attempts/1

Artifact

Subject: cueapi-0.2.0.tar.gz
SHA-256 checksum: fb4874066aa2a5b9613f908f829c55ec452bbc8334d22e28fd4c473ed4eeaccc Verifying attestations

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.