Paste it in your chat with your agent

// Cloud. Laptop. Mac Mini. NAT. Same primitive.

Coordination infrastructure for agent systems.

Connect any step, task, job, or agent across any environment. Every handoff verified.

terminal
# Your agent. On time. Every time.
curl -X POST https://api.cueapi.ai/v1/cues \
-H "Authorization: Bearer cue_sk_..." \
-H "Content-Type: application/json" \
-d '{"name":"morning-briefing",
"schedule":{"type":"recurring","cron":"0 9 * * *"},
"callback":{"url":"https://your.agent/run"}}'
 
# HTTP 200
{ "id": "cue_a3f9b2...", "status": "active" }

THE PRIMITIVES

Five primitives. One journey.

Every scheduled run passes through these five stages. Each primitive is one station on the rail.

INTENT
01

Cue

Schedule lives in CueAPI. Survives every restart and deploy.

EXAMPLEcron 0 9 * * *
before T = 0
FIRE
02

Execution

One row per firing. Status, attempts, outcome all attach here.

EXAMPLEexec_a3f9b2c8
T = 09:00:00
REACH
03

Worker

Agent pulls its work. Reaches behind NAT, firewalls, laptops.

EXAMPLElaptop, behind NAT
T = 09:00:02
REPORT
04

Outcome

Handler POSTs back what happened. Closes the execution record.

EXAMPLEsuccess
T = 09:02:17
PROVE
05

Evidence

Structured fields on the outcome. Verified against the cue rule.

EXAMPLEgithub.com/org/repo/pull/42
T = 09:02:17

One run. Five stations. No silence between.

HOW IT WORKS

Agents coordinate through cues.

One agent finishes. Its outcome fires the next cue. The next worker catches. No scheduler between them, no glue code, no polling.

Chain in actionClaude Code ships staging. QA catches, tests, ships next.
Live chain. Agents passing the baton.
executions

IN THE WILD

The shapes cues take.

Content machines. Build pipelines. Creative stacks. Agent factories. Cross-agent meshes. Same primitive underneath, six different chains on top.

AGENT MESH

A nervous system for agents.

Every agent talks through a cue bus. No middleware, no polling. Outcomes flow, the mesh forms itself.

CI / CD

Commit to prod, with proof.

Push fires tests. Build fires deploy. Every stage leaves evidence, not just a green check.

CONTENT MACHINES

Research. Draft. Edit. Ship.

One agent researches. Another drafts. An editor polishes. A publisher fans out. Every revision recorded.

CREATIVE STACKS

Image, audio, video. One take.

Brief fires every creative agent in parallel. Image, voice, edit work their tracks. Output assembles itself.

SOFTWARE PRODUCTION

Spec in. Ship out.

Claude codes from the spec. A QA agent tests. Passing code ships and reports back.

AGENT FACTORY

Agents that build agents.

One agent writes the next. A tester runs it against a suite. A deployer puts it live. Your factory floor, on cue.

CODE & CLI

Five minutes from install to first cue.

Any language on the left. Any shell on the right. Pick your surface.

# Create a cue
curl -X POST https://api.cueapi.ai/v1/cues \
-H "Authorization: Bearer cue_sk_..." \
-H "Content-Type: application/json" \
-d '{
"name": "morning-analytics",
"schedule": {
"type": "recurring",
"cron": "0 9 * * *",
"timezone": "America/Los_Angeles"
},
"callback": {"url": "https://my-agent.com/webhook"},
"payload": {"task": "pull-dashboard"}
}'
 
# 201 Created
{"id": "cue_x7k9m2p4q8w1", "status": "active"}
zsh

PATTERNS

What teams build on Cue.

Morning Handoff agent use case iconMorning Handoff
Content Chain agent use case iconContent Chain
Follow-Up Loop agent use case iconFollow-Up Loop
Silent-Failure Watch agent use case iconSilent-Failure Watch
Multi-Agent Orchestrator agent use case iconMulti-Agent Orchestrator
Cross-System Sync agent use case iconCross-System Sync
Digest Pipeline agent use case iconDigest Pipeline
Invoice Workflow agent use case iconInvoice Workflow
Code Review Loop agent use case iconCode Review Loop
Report Pipeline agent use case iconReport Pipeline
Churn Signal Chain agent use case iconChurn Signal Chain
Backup Verification agent use case iconBackup Verification

OPEN SOURCE

The whole primitive. Apache 2.0.

Cue is open infrastructure. docker compose up boots the full stack: API, poller, worker, Postgres, Redis. Same verification. Same workers. Same REST surface. Self-host your coordination, or use the hosted service.

View on GitHub →
cueapi/cueapi-core
600+
tests
Apache 2.0
license
100%
parity
1
docker compose up

SECURITY & PRIVACY

Built for trust, not theater.

Defense in depth. Five layers, core outward, every claim verifiable.

TRUST
Open sourceApache 2.0, inspectable
600+ tests50+ security-specific
Honest disclosureno SOC 2, no paid audit
PRIVACY
GDPR data rightsdeletion, export via API
US state privacy18 laws incl. CCPA
Zero cookiesno tracking, no banner
BOUNDARY
SSRF protection11 blocked IP ranges
Replay protection5-minute signature window
Audit trailevery event logged
TRANSPORT
Signed webhooksHMAC-SHA256 per delivery
HTTPS onlyno plaintext endpoints
STORAGE
Hashed API keysSHA-256 at rest

Full details at cueapi.ai/security and cueapi.ai/privacy.

CueAPI coordination infrastructure logo

Start coordinating.

pip install cueapi. First cue in 60 seconds. Free forever to start.

How do I know if my agent ran successfully?
Ctrl+K